-
Notifications
You must be signed in to change notification settings - Fork 2k
enhancement(elasticsearch sink): Retry whole payload on partial bulk failure #14891
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
Conversation
Signed-off-by: Kruno Tomola Fabro <krunotf@gmail.com>
Signed-off-by: Kruno Tomola Fabro <krunotf@gmail.com>
✅ Deploy Preview for vector-project ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
neuronull
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution!
Looking good just dropped some mostly minor initial observations:
Co-authored-by: neuronull <kyle.criddle@datadoghq.com>
✅ Deploy Preview for vrl-playground canceled.
|
Co-authored-by: neuronull <kyle.criddle@datadoghq.com>
Signed-off-by: Kruno Tomola Fabro <krunotf@gmail.com>
Signed-off-by: Kruno Tomola Fabro <krunotf@gmail.com>
|
I just noticed this question:
I think it is ok where it is? Tagging @spencergilbert and @jszwedko for thoughts on that. |
Soak Test ResultsBaseline: ac69a47 ExplanationA soak test is an integrated performance test for vector in a repeatable rig, with varying configuration for vector. What follows is a statistical summary of a brief vector run for each configuration across SHAs given above. The goal of these tests are to determine, quickly, if vector performance is changed and to what degree by a pull request. Where appropriate units are scaled per-core. The table below, if present, lists those experiments that have experienced a statistically significant change in their throughput performance between baseline and comparision SHAs, with 90.0% confidence OR have been detected as newly erratic. Negative values mean that baseline is faster, positive comparison. Results that do not exhibit more than a ±8.87% change in mean throughput are discarded. An experiment is erratic if its coefficient of variation is greater than 0.3. The abbreviated table will be omitted if no interesting changes are observed. Changes in throughput with confidence ≥ 90.00% and absolute Δ mean >= ±8.87%:
Fine details of change detection per experiment.
|
|
The file to black hole soak regression is expected, it's been addressed on master which this branch hasn't pulled that change in yet. Let's roll with the current placement of Thanks @ktff ! |
We discussed this internally and the consensus was to roll with the current placement for now since future changes to it should still be able to maintain backwards comparability. We might consider adding a wrapper type that includes the shared config struct along with the ES specific option. |
Soak Test ResultsBaseline: 943c616 ExplanationA soak test is an integrated performance test for vector in a repeatable rig, with varying configuration for vector. What follows is a statistical summary of a brief vector run for each configuration across SHAs given above. The goal of these tests are to determine, quickly, if vector performance is changed and to what degree by a pull request. Where appropriate units are scaled per-core. The table below, if present, lists those experiments that have experienced a statistically significant change in their throughput performance between baseline and comparision SHAs, with 90.0% confidence OR have been detected as newly erratic. Negative values mean that baseline is faster, positive comparison. Results that do not exhibit more than a ±8.87% change in mean throughput are discarded. An experiment is erratic if its coefficient of variation is greater than 0.3. The abbreviated table will be omitted if no interesting changes are observed. No interesting changes in throughput with confidence ≥ 90.00% and absolute Δ mean >= ±8.87%: Fine details of change detection per experiment.
|
…failure (#14891) Adds a new config option for the elasticsearch sink (request_retry_partial), which is disabled by default but when enabled, retries the whole payload on partial bulk failure if the partial failure contains a retriable status.
Ref: #140
Retries whole payload on partial bulk failure if partial failure contains retriable status. At the moment those are:
Adds option
request_retry_partialto enable this behavior. It's disabled by default.Open questions
request_retry_partial? Adding it torequest.*option set would also add it to all of the other http based sinks. (EDIT: Let's keep it at current placement for now.)cc. @jszwedko , @sim0nx