[FLINK-23418][e2e] Increase the timeout to make kubernetes application ha test more stable #16602
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.
What is the purpose of the change
The test
test_kubernetes_application_ha.sh
could fail because of timeout(30s) waiting for logRestoring job 00000000000000000000000000000000 from Checkpoint
. I did not find any exceptions, potential bugs for Kubernetes HA and recovery process. It just seems that the JobManager started and recovered slowly. This PR will increase the timeout to 120s to make the test more stable.Brief change log
Verifying this change
test_kubernetes_application_ha.sh
Does this pull request potentially affect one of the following parts:
@Public(Evolving)
: (yes / no)Documentation