[GitHub] [pulsar] Hongten commented on issue #4162: kubectl appply -f bookie.yaml andthen Error

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

Hongten commented on issue #4162:
URL: https://github.com/apache/pulsar/issues/4162#issuecomment-1156181776

   **Solution**
   My solution is to remove the bookie PVC first. And redeploy the chart again. The new PVC will be created. Note: **The PVC save the data, you need to know the risk when you delete it.**
   ```
   kubectl get pvc -n <your-namespace>
   kubectl delete pvc <pvc-name> -n <your-namespace>
   ```
   
   
   **Root cause**
   - The old PVC has the historical data which includes the instanceID under the `/pulsar/data/bookkeeper/ledgers/current/VERSION`(This is my ledger dir)(The old InstanceID)
   - After I change the zookeeper address, the pulsar will init the pulsar cluster with the new INSTENCEID. You can find the new INSTANCEID under `/ledgers/INSTANCEID` in the zookeeper(The new InstanceID)
   - The new instanceID and the old instanceID are different.
   
   **Details**
   I encountered the same issue with pulsar-2.9.2 version. In my case, I use the helm charts to create a pulsar cluster on the k8s cluster, and it run successfully. 
   
   I want to use the outside zookeeper cluster to replace the current zk cluster(running on k8s with pulsar). So I change the values.yaml file. And deploy it into k8s. Then encountered this issue.
   ```
   components.zookeeper=false
   userProvidedZookeepers="outside-zk-nodes:9092"
   ```


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

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