-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Merged
Merged
Changes from all commits
Commits
Show all changes
22 commits
Select commit
Hold shift + click to select a range
2004803
Make RetryOnStatus configurable and default to 429 only
carsonip c850e70
Add changelog
carsonip a9b7f40
Update changelog
carsonip 00be1be
Update changelog
carsonip 48ff096
Make it clear that the status codes are shared between request and do…
carsonip bc562d7
Update exporter/elasticsearchexporter/integrationtest/datareceiver.go
carsonip 79eb355
Remove redundant nil check
carsonip d76a961
More descriptive status codes
carsonip ae3d0bf
Be specific about how to opt in to the previous behavior
carsonip 779fa85
Merge branch 'main' into retry-on-status
carsonip c1d2d3f
Change default to avoid breaking change
carsonip 5180e22
Fix tests
carsonip c8bc06f
Update readme
carsonip bbea200
Update changelog
carsonip e3e6693
Add warning in readme
carsonip 6a1f05c
Merge branch 'main' into retry-on-status
carsonip a31d74d
Merge branch 'main' into retry-on-status
carsonip a2ba0ea
Merge branch 'main' into retry-on-status
carsonip 8c4ba0d
Merge branch 'main' into retry-on-status
carsonip bc5e3f6
Merge branch 'main' into retry-on-status
carsonip 0997858
Merge branch 'main' into retry-on-status
carsonip abe1b81
Merge branch 'main' into retry-on-status
codeboten File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
# Use this changelog template to create an entry for release notes. | ||
|
||
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix' | ||
change_type: enhancement | ||
|
||
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver) | ||
component: elasticsearchexporter | ||
|
||
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). | ||
note: Add retry.retry_on_status config | ||
|
||
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists. | ||
issues: [32584] | ||
|
||
# (Optional) One or more lines of additional information to render under the primary note. | ||
# These lines will be padded with 2 spaces and then inserted directly into the document. | ||
# Use pipe (|) for multiline entries. | ||
subtext: | | ||
Previously, the status codes that trigger retries were hardcoded to be 429, 500, 502, 503, 504. | ||
It is now configurable using `retry.retry_on_status`, and defaults to `[429, 500, 502, 503, 504]` to avoid a breaking change. | ||
To avoid duplicates, it is recommended to configure `retry.retry_on_status` to `[429]`, which would be the default in a future version. | ||
|
||
# If your change doesn't affect end users or the exported elements of any package, | ||
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label. | ||
# Optional: The change log or logs in which this entry should be included. | ||
# e.g. '[user]' or '[user, api]' | ||
# Include 'user' if the change is relevant to end users. | ||
# Include 'api' if there is a change to a library API. | ||
# Default: '[user]' | ||
change_logs: [user] |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -23,6 +23,7 @@ type elasticsearchTracesExporter struct { | |
logstashFormat LogstashFormatSettings | ||
dynamicIndex bool | ||
maxAttempts int | ||
retryOnStatus []int | ||
|
||
client *esClientCurrent | ||
bulkIndexer esBulkIndexerCurrent | ||
|
@@ -63,6 +64,7 @@ func newTracesExporter(logger *zap.Logger, cfg *Config) (*elasticsearchTracesExp | |
index: cfg.TracesIndex, | ||
dynamicIndex: cfg.TracesDynamicIndex.Enabled, | ||
maxAttempts: maxAttempts, | ||
retryOnStatus: cfg.Retry.RetryOnStatus, | ||
model: model, | ||
logstashFormat: cfg.LogstashFormat, | ||
}, nil | ||
|
@@ -122,5 +124,5 @@ func (e *elasticsearchTracesExporter) pushTraceRecord(ctx context.Context, resou | |
if err != nil { | ||
return fmt.Errorf("Failed to encode trace record: %w", err) | ||
} | ||
return pushDocuments(ctx, e.logger, fIndex, document, e.bulkIndexer, e.maxAttempts) | ||
return pushDocuments(ctx, e.logger, fIndex, document, e.bulkIndexer, e.maxAttempts, e.retryOnStatus) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Everything looks good, BTW, the |
||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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.