[GitHub] [pulsar-helm-chart] haorenfsa removed a comment on issue #124: pulsar waiting to start: PodInitializing

[GitBox <gi...@apache.org>]

haorenfsa removed a comment on issue #124:
URL: https://github.com/apache/pulsar-helm-chart/issues/124#issuecomment-975045783


   In the `pulsar-init` Job, the init script is:
   ``` shell
   bin/pulsar initialize-cluster-metadata \
                   --cluster pulsar \
                   --zookeeper pulsar-zookeeper:2181 \
                   --configuration-store pulsar-zookeeper:2181 \
                   --web-service-url http://pulsar-broker.test.svc.cluster.local:8080/ \
                   --web-service-url-tls https://pulsar-broker.test.svc.cluster.local:8443/ \
                   --broker-service-url pulsar://pulsar-broker.test.svc.cluster.local:6650/ \
                   --broker-service-url-tls pulsar+ssl://pulsar-broker.test.svc.cluster.local:6651/ || true;
   ```
   
   The `|| true` at the end makes the Job not fail even when error occurs in initializing metadata.
   
   Usually it's ok, for there's a init container checking zookeeper status, but if we have a bad day when zookeeper goes done just after init container run, and before main container start, the cluster metadata will never be initialized. The pulsar components will all be blocked forever.
   
   We should remove the tail `|| true`, let the job restart if failed.


-- 
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: dev-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org