This message was deleted.
# general
s
This message was deleted.
d
You have a few options; the best approach depends on the test you are trying to run. If the test is part of an automated suite of integration tests, then you should just use the Pulsar test container.
The docker-compose solution is also a good option if you want to avoid customizing your standalone deployment to incorporate Zookeeper.
l
I think that the initial error was because it’s waiting on the port 2181 to respond in the previous version (Zookeeper) and now this port is no longer used by RockDb it seems
d
If you want to stick with the standalone option, then will need to change Pulsar configurations and start Pulsar, by passing environment variables with the
PULSAR_PREFIX_
prefix, e.g.
docker run -it -e PULSAR_PREFIX_xxx=yyy -p 6650:6650  -p 8080:8080 --mount source=pulsardata,target=/pulsar/data --mount source=pulsarconf,target=/pulsar/conf apachepulsar/pulsar:2.10.0 sh -c "bin/apply-config-from-env.py conf/standalone.conf && bin/pulsar standalone
l
So maybe the simple first step is to remove that ping on the test…
ah yes, I did some experimenting with that ☝️
Still new to Pulsar, so don’t want to overwhelm the channel with too many dumb questions… but I started to go nuts…
d
You will have to change the following properties to use ZK as the metadata store;
metadataStoreUrl
,
metadataStoreConfigPath
It’s all good. That’s why we are here.
l
But that’s if I want to use ZK… Maybe I can run the tests on that library without ZK and use the default metadata store of the standalone image?
d
FWIW, I prefer the docker-compose approach, as it is more aligned with an actual deployment and gives me more flexibility. Here is how I structure things in my projects.
Yes, if you don’t need ZK, then the default metadata store for the standalone will work fine.
l
What’s the rationale for switching to ZK? That’s when I run multiple brokers?
Looks like I fixed my 2nd issue issue related to this… Changed
Copy code
bin/pulsar initialize-transaction-coordinator-metadata -cs standalone:2181 -c standalone --initial-num-transaction-coordinators 2
into
Copy code
bin/pulsar initialize-transaction-coordinator-metadata -cs rocksdb:///pulsar/data/metadata -c standalone --initial-num-transaction-coordinators 2
and it did not yell at me for once 😄
➕ 1
d
Yes, if you want to simulate multiple brokers, test out automatic load balancing, etc.
l
Thanks David!!! Much appreciated
👍 1