iampranabroy opened a new issue, #477:
URL: https://github.com/apache/solr-operator/issues/477
#### Describe the issue:
When deploying SolrCloud via Apache Solr Operator with ensembled Zookeeper,
sometimes one of the zookeeper pods gives the below error during the start:
```
2021-03-29 13:33:56,645 [myid:2] - ERROR [main:QuorumPeerMain@113] -
Unexpected exception, exiting abnormally
java.lang.RuntimeException: My id 2 not in the peer list
at
org.apache.zookeeper.server.quorum.QuorumPeer.start(QuorumPeer.java:1073)
at
org.apache.zookeeper.server.quorum.QuorumPeerMain.runFromConfig(QuorumPeerMain.java:227)
at
org.apache.zookeeper.server.quorum.QuorumPeerMain.initializeAndRun(QuorumPeerMain.java:136)
at
org.apache.zookeeper.server.quorum.QuorumPeerMain.main(QuorumPeerMain.java:90)
```
#### Possible solutions:
As per the discussions in the GitHub
[**issue-315**](https://github.com/pravega/zookeeper-operator/issues/315#issuecomment-824555225),
they are suggesting increasing the `probes.readiness.initialDelaySeconds` from
default `10` to `30/60` sec.
Can we add support for the zookeeper `config.*`
[**parameters**](https://github.com/pravega/zookeeper-operator/tree/v0.2.14/charts/zookeeper#configuration)
in Apache Solr Operator helm charts?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
