[CN-634] Add client recreation logic for times client cannot access the cluster #500
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
mtyazici
requested review from
SeriyBg and
cagric0
and removed request for
a team
github-actions
bot
added
enhancement
cagric0
approved these changes
Dec 14, 2022
SeriyBg
approved these changes
Dec 19, 2022
mtyazici
force-pushed
the
cn-634
branch
2 times, most recently
from
8f4de81
to
27f9ba8
Compare
mtyazici
changed the title
mtyazici
removed
the
fix
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.
Description
Changes:
User Impact
Operator will restart the Hazelcast client when the cluster is inaccessible.