[DM-46595] Review metric_batch_size configuration in Sasquatch #3751
Conversation
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
- Also change pull policy to IfNotPresent
- They were split in DM-46203 to alleviate the race condition found in the Telegraf Avro parsers. This is fixed in the new image.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In DM-46463 we reduced the
metric_batch_sizeconfiguration to 2500 to fix the error at BTS. This was seen later at USDF and Summit with the M1M3 connector where we reduced metric_batch_size even further to 1000 messages.This ticket makes metric_batch_size = 1000 the default configuration in all environments.