You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(Describe the feature, bug, question, proposal that you are requesting)
In cases where ZKserver takes little bit more time to startup, "echo ruok | nc 127.0.0.1 $CLIENT_PORT" fails with connection refused. ZookeeperReady.sh doesn't promote the node as participant and the quorum doesn't form
Importance
(Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have))
blocker as the zk-2/zk-3 pod goes in to error state, doesn't get promoted as participant and the quorum is not formed
Location
(Where is the piece of code, package, or document affected by this issue?)
ZK cluster CRD POD configuration
Suggestions for an improvement
please make the initialdelayseconds configurable through CRD so some delay can be introduced (How do you suggest to fix or proceed with this issue?)
The text was updated successfully, but these errors were encountered:
Description
(Describe the feature, bug, question, proposal that you are requesting)
In cases where ZKserver takes little bit more time to startup, "echo ruok | nc 127.0.0.1 $CLIENT_PORT" fails with connection refused. ZookeeperReady.sh doesn't promote the node as participant and the quorum doesn't form
Importance
(Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have))
blocker as the zk-2/zk-3 pod goes in to error state, doesn't get promoted as participant and the quorum is not formed
Location
(Where is the piece of code, package, or document affected by this issue?)
ZK cluster CRD POD configuration
Suggestions for an improvement
please make the initialdelayseconds configurable through CRD so some delay can be introduced
(How do you suggest to fix or proceed with this issue?)
The text was updated successfully, but these errors were encountered: