Issue 482: Reevaluating number of client connections dynamically in the teardown script #483
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.
Signed-off-by: Nishant Gupta Nishant_Gupta3@dell.com
Change log description
Currently the CONN_COUNT variable is only evaluated once in the zookeeperTeardown.sh script
As a result, the loop would always take 30 seconds if there were client connections present when the script started to run, and ZK pod would terminate with 137 error code with the default termination grace period set to 30s. Need to make sure CONN_COUNT gets reevaluated every cycle and allows the code to break out of the loop earlier.
Purpose of the change
Fixes #482
What the code does
Moves the CONN_COUNT variable inside the for loop
How to verify it
All e2e should pass