Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[exporter/elasticsearch] Add retry.retry_on_status config #32585
[exporter/elasticsearch] Add retry.retry_on_status config #32585
Changes from 5 commits
2004803
c850e70
a9b7f40
00be1be
48ff096
bc562d7
79eb355
d76a961
ae3d0bf
779fa85
c1d2d3f
5180e22
c8bc06f
bbea200
e3e6693
6a1f05c
a31d74d
a2ba0ea
8c4ba0d
bc5e3f6
0997858
abe1b81
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
On a seperate note, should
EnableRetryOnTimeout
be equal to!retryDisabled
?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.
I checked the v7 estransport and EnableRetryOnTimeout usage is wrapped inside MaxRetries. Therefore, in practice, changing it to
!retryDisabled
will have no effect. But I agree that it will be clearer to do so. Let me make the change.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.
hmm, I've changed my mind. The default in go-elasticsearch for DisableRetry and EnableRetryOnTimeout are both false, which makes sense. As a user I would not expect the client to retry the bulk request on timeout. Let me separate this discussion into an issue, whether the existing setting to enable retry on timeout to
config.Retry.Enabled
is desirable.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.
Everything looks good, BTW, the
pushDocuments
function is loaded with too many arguments now. Hopefully, it will shrink in the future :-P.