You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pulsar.apache.org by GitBox <gi...@apache.org> on 2021/11/22 05:07:24 UTC

[GitHub] [pulsar-helm-chart] haorenfsa opened a new issue #175: Create may block if the initialize cluster job fails

haorenfsa opened a new issue #175:
URL: https://github.com/apache/pulsar-helm-chart/issues/175


   **Describe the bug**
   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 down just after init container succeeded, 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.
   
   **To Reproduce**
   Steps to reproduce the behavior:
   `TBD`
   
   **Expected behavior**
   init Job will keep retrying when initializing metadata failed, until success.
   
   **Screenshots**
   `TBD`
   
   **Desktop (please complete the following information):**
    - OS: KinD on OS.X
   
   **Additional context**
   ref: milvus-io/milvus-operator#40
   
   


-- 
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



[GitHub] [pulsar-helm-chart] lhotari closed issue #175: Create may block if the initialize cluster job fails

Posted by GitBox <gi...@apache.org>.
lhotari closed issue #175:
URL: https://github.com/apache/pulsar-helm-chart/issues/175


   


-- 
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



[GitHub] [pulsar-helm-chart] haorenfsa commented on issue #175: Create may block if the initialize cluster job fails

Posted by GitBox <gi...@apache.org>.
haorenfsa commented on issue #175:
URL: https://github.com/apache/pulsar-helm-chart/issues/175#issuecomment-975138262


   I'm wondering why did we have this `|| true;` in the first place. Is it a trick for something or just a typo?


-- 
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