otmanel31 opened a new issue #10385:
URL: https://github.com/apache/pulsar/issues/10385


   **Describe the bug**
   After trying to migrate from apache pulsar 2.7.0 to 2.8 version, i face some 
issues on runtime:
   Pulsar is deployed in a k8s deployement ( not in standalone)
   I build apache pulsar 2.8  by my self by exeecuting mvn build of pulsar 
project ( " mvn -Pcore-modules -T 1C clean install -DskipTests 
-Dspotbugs.skip=true).
   Then, i execute docker build file that is under docker folder in order to 
build and push docker images into my private registry
   
   After changing image in my yml config , i face below issues on runtime:
   in bookie:
   - org.apache.bookkeeper.util.DiskChecker$DiskErrorException: directory is 
not writable: /pulsar/data/bookkeeper/ledgers/current
   
   in zookie:
   - org.apache.zookeeper.server.persistence.FileTxnSnapLog$DatadirException: 
Cannot write to data directory /pulsar/data/zookeeper/version-2
   
   Any hints about what does that mean ? did i make something bad during build 
steps ? as in bookie and zookie deployment it seems to be writable right ... 
   
   I would like to specify i didn't face this issues when i test my build in 
standalone mode.
   
   **To Reproduce**
   Steps to reproduce the behavior:
   1. move from 2.7.0 to 2.8.0 version
   2. restart pulsar bookkie, zookkie, broker, proxy one by one
   3. check logs
   
   **Screenshots**
   bookkie screenshot:
   
![image](https://user-images.githubusercontent.com/25247382/116089029-bb2af700-a6a2-11eb-8605-83272caf328e.png)
   
   zookkie screenshot:
   
![image](https://user-images.githubusercontent.com/25247382/116089954-a7cc5b80-a6a3-11eb-8c3d-bd89ca54f61a.png)
   
   
   **Desktop (please complete the following information):**
    - OS: linux
    - maven 3.6.3
    - jdk used to build: openjdk8
   
   


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

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to