-
Notifications
You must be signed in to change notification settings - Fork 327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
precondition failed for splits #5431
Comments
@trinity-1686a any idea what happened here? |
the error message is a bit misleading. iiuc, this error happens when a split was expected to be Do you know if some of your indexes have the same node_id? (either explicitly configured, or same short hostname)? If you search for |
The split 01J7WT2D80WANG4V0EN4FVZHKF is present only in the quickwit-indexer-27 and metastore logs.
|
Also in the affected index the "timestamp range start" not equal to "Timestamp range end " - retention
|
How likely a logs with the timestamp older than now() - "retention days" may break the retention logic ? |
the retention logic looks at the timestamp range end (of individual splits). |
we started to drop logs with timestamp in the far past on the fluent-bit side and the issue has been resolved. |
Hi,
We have 4 indexes in quickwit, all indexes are in GCS, quickwit version 0.8.2.
Recently started issue with the biggest index fluentbit-logs-2024-09-12 when splits older 1h is automatically removed. Other indexes are ok. The issue is not gone after the index recreation.
The affected index has way more Staged splits than other indexes.
In the indexer logs the only errors:
index config
The text was updated successfully, but these errors were encountered: