michaeljmarshall commented on issue #15647:
URL: https://github.com/apache/pulsar/issues/15647#issuecomment-1354277105
I think I just figured it out!
When I run `docker run -it -p 6650:6650 -p 8080:8080 --mount
source=pulsardata,target=/pulsar/data --mount
source=pulsarconf,target=/pulsar/conf apachepulsar/pulsar:2.10.2 bin/pulsar
standalone`, it works on my MacOS with an intell chip.
However, that is when I am using a new `pulsardata` volume. If you use an
existing volume that was run with an older version of pulsar, it fails. I
reproduced this by first running:
1. `docker run -it -p 6650:6650 -p 8080:8080 --mount
source=pulsardatax,target=/pulsar/data --mount
source=pulsarconf,target=/pulsar/conf apachepulsar/pulsar:2.8.2 bin/pulsar
standalone`
2. `docker run -it -p 6650:6650 -p 8080:8080 --mount
source=pulsardatax,target=/pulsar/data --mount
source=pulsarconf,target=/pulsar/conf apachepulsar/pulsar:2.10.2 bin/pulsar
standalone`
Technically step 1 failed on me for unrelated reasons, but it was able to
initialize the zookeeper directories with the old filesystem permissions. Then,
when I ran command 2, I reproduced the problematic behavior:
```
2022-12-16T06:18:37,740+0000 [main] ERROR
org.apache.pulsar.zookeeper.LocalBookkeeperEnsemble - Exception while
instantiating ZooKeeper
org.apache.zookeeper.server.persistence.FileTxnSnapLog$DatadirException:
Cannot write to data directory data/standalone/zookeeper/version-2
at
org.apache.zookeeper.server.persistence.FileTxnSnapLog.<init>(FileTxnSnapLog.java:140)
~[org.apache.zookeeper-zookeeper-3.6.3.jar:3.6.3]
at
org.apache.zookeeper.server.ZooKeeperServer.<init>(ZooKeeperServer.java:441)
~[org.apache.zookeeper-zookeeper-3.6.3.jar:3.6.3]
at
org.apache.pulsar.zookeeper.LocalBookkeeperEnsemble.runZookeeper(LocalBookkeeperEnsemble.java:201)
~[org.apache.pulsar-pulsar-broker-2.10.2.jar:2.10.2]
at
org.apache.pulsar.zookeeper.LocalBookkeeperEnsemble.startStandalone(LocalBookkeeperEnsemble.java:444)
~[org.apache.pulsar-pulsar-broker-2.10.2.jar:2.10.2]
at org.apache.pulsar.PulsarStandalone.start(PulsarStandalone.java:269)
~[org.apache.pulsar-pulsar-broker-2.10.2.jar:2.10.2]
at
org.apache.pulsar.PulsarStandaloneStarter.main(PulsarStandaloneStarter.java:143)
~[org.apache.pulsar-pulsar-broker-2.10.2.jar:2.10.2]
2022-12-16T06:18:37,755+0000 [main] ERROR
org.apache.pulsar.PulsarStandaloneStarter - Failed to start pulsar service.
java.io.IOException:
org.apache.zookeeper.server.persistence.FileTxnSnapLog$DatadirException: Cannot
write to data directory data/standalone/zookeeper/version-2
at
org.apache.pulsar.zookeeper.LocalBookkeeperEnsemble.runZookeeper(LocalBookkeeperEnsemble.java:215)
~[org.apache.pulsar-pulsar-broker-2.10.2.jar:2.10.2]
at
org.apache.pulsar.zookeeper.LocalBookkeeperEnsemble.startStandalone(LocalBookkeeperEnsemble.java:444)
~[org.apache.pulsar-pulsar-broker-2.10.2.jar:2.10.2]
at org.apache.pulsar.PulsarStandalone.start(PulsarStandalone.java:269)
~[org.apache.pulsar-pulsar-broker-2.10.2.jar:2.10.2]
at
org.apache.pulsar.PulsarStandaloneStarter.main(PulsarStandaloneStarter.java:143)
~[org.apache.pulsar-pulsar-broker-2.10.2.jar:2.10.2]
Caused by:
org.apache.zookeeper.server.persistence.FileTxnSnapLog$DatadirException: Cannot
write to data directory data/standalone/zookeeper/version-2
at
org.apache.zookeeper.server.persistence.FileTxnSnapLog.<init>(FileTxnSnapLog.java:140)
~[org.apache.zookeeper-zookeeper-3.6.3.jar:3.6.3]
at
org.apache.zookeeper.server.ZooKeeperServer.<init>(ZooKeeperServer.java:441)
~[org.apache.zookeeper-zookeeper-3.6.3.jar:3.6.3]
at
org.apache.pulsar.zookeeper.LocalBookkeeperEnsemble.runZookeeper(LocalBookkeeperEnsemble.java:201)
~[org.apache.pulsar-pulsar-broker-2.10.2.jar:2.10.2]
... 3 more
```
For anyone following this thread, what happens when you try using a fresh
volume?
> Hello, I got this error when I run docker pulsar standalone.(I've try to
use 2.8.X,and it occurs another errors)
For reference, this comment was extremely helpful. It made me realize that
trying different versions together might lead to conflicts. Thanks @leosanqing!
--
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]
