Closed dnhatn closed 3 days ago
Pinging @elastic/es-analytical-engine (Team:Analytics)
Thanks @smalyshev.
Status | Branch | Result |
---|---|---|
❌ | 8.17 | Commit could not be cherrypicked due to conflicts |
✅ | 8.x |
You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 117592
Currently, we have three clients fetching pages by default, each with its own lifecycle. This can result in scenarios where more than one request is sent to complete the remote sink. While this does not cause correctness issues, it is inefficient, especially for cross-cluster requests. This change tracks the status of the remote sink and tries to send only one finish request per remote sink.