Optimize error handling after lazy rollovers #108838
Labels
:Data Management/Data streams
Data streams and their lifecycles
:Data Management/Ingest Node
Execution or management of Ingest Pipelines including GeoIP
>refactoring
Team:Data Management
Meta label for data/management team
Currently, we're looping over all the requests in the bulk request for each failed lazy rollover (here, and once #108108 is merged, we'll do it in
BulkOperation
too). While this is probably around O(n) in practice, it's technically O(n^2), if each document was destined to a different failure store and each rollover failed.A better alternative would be to collect all the failed rollovers and traverse the documents one time.
The text was updated successfully, but these errors were encountered: