feat: new variable to control Kafka URP topics retries #1868
+13
−2
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.
Description
This PR makes it possible to configure the number of retries while waiting for URP topics to stabilize during Kafka health checks.
We are using the health checks tasks when OS-patching our clusters. For some major patches that require a node reboot, a restarted broker needs more time to catch up on replicating partitions. With the current settings, this fails the play, which also wastes a lot of resources on fetching log files for troubleshooting (not required). We think the number of retries while waiting for URP topics to stabilize should be configurable - as it will depend on the cluster load.
Fixes # (issue)
Type of change
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist: