trinity-1686a

the idea is to store posting lists directly inside of the sstables (in place of term info) in the case where a term appears only once.

we already have retries on the storage for writes, up to 5 times. Some error were not retried, but now are since https://github.com/quickwit-oss/quickwit/pull/5384, so I think this ticket can be...

we retry based on what the sdk defines as transient and throttling errors, list here: https://docs.rs/aws-runtime/1.4.3/src/aws_runtime/retries/classifiers.rs.html#18-36 It doesn't include InternalError, so we don't retry on that

we do retry upload now for all transient errors we could find. If more error conditions should be retried, that should be a separate ticket

the commit is bd72e1f9dbe59fc03f48824099252f65a1ceab63 . I don't think it's in a state to be merged. This warns on transient errors, including those that would be retried automatically (which was the...

i don't think we want to do anything. Normal errors seem to already be logged. Afaict, the errors that caught someone's eyes were just transient errors (rate limiting) that increased...

related to https://github.com/quickwit-oss/tantivy/issues/2380

do you happen to know when does the issue resolve by itself? Is that on node restart, or possibly when ingesting plan or something like that evolves?

looks like this made `actors::merge_executor::tests::test_delete_all` very flaky. I suspect this is because when no split is published, the merge might not get acknowledged properly to the Tracker

currently this makes one test very flaky (fails more often than not) and i haven't figured out why yet. i'd rather fix that before merging