<@U078Y59KC3B> after launching the standalone Puls...
# ask-ai
n
@RunLLM after launching the standalone Pulsar cluster, the pulsar-proxy errors out with “Error from server (BadRequest): container “pulsar-proxy” in pod “pulsar-proxy-0" is waiting to start: PodInitializing”. What is wrong? Can I inspect the logs of the wait-zookeeper-ready container that is running inside of it? Zookeeper is up and running, as are all other services.
r
It seems likely that the issue with the
pulsar-proxy
pod being stuck in the "PodInitializing" state could be related to the initialization process or configuration issues. You can inspect the logs of the
wait-zookeeper-ready
container to get more insights into what might be causing the delay or failure in initialization. To inspect the logs of the
wait-zookeeper-ready
container, you can use the following command:
Copy code
kubectl logs pulsar-proxy-0 -c wait-zookeeper-ready -n namespace
Replace
namespace
with the appropriate namespace where your Pulsar cluster is deployed. This command will show you the logs of the
wait-zookeeper-ready
container, which might provide more information on why the
pulsar-proxy
is not starting properly. If you need more detailed guidance, please let me know. Sources: - GitHub Issue #21974 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.
n
@RunLLM i have changed the zookeeper port. how do I tell the proxy to use this new port?
r
It seems likely that to configure the Pulsar proxy to use a new ZooKeeper port, you need to update the
metadataStoreUrl
and
configurationMetadataStoreUrl
in the
proxy.conf
file with the new port number. According to the Pulsar documentation, these settings specify the ZooKeeper connection details for the proxy. Here's an example of how you might update the
proxy.conf
file:
Copy code
metadataStoreUrl = my-zk-0:NEW_PORT,my-zk-1:NEW_PORT,my-zk-2:NEW_PORT
configurationMetadataStoreUrl = my-zk-0:NEW_PORT,my-zk-1:NEW_PORT,my-zk-2:NEW_PORT
Replace
NEW_PORT
with the new port number you have configured for ZooKeeper. Would you like more detailed instructions? Sources: - Pulsar documentation 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.
n
@RunLLM how do i set this in the value.yaml when launching the helm chart?
r
I'm not able to find any data sources to answer your question. You might want to specify which Helm chart you are using or provide more details about your deployment setup. If this doesn't help, please reach out to the StreamNative support team for further assistance. 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.
n
@RunLLM can you give me an example of a custom configurationStore to put in the
pulsar_metadata
section?
r
To configure a custom
configurationMetadataStoreUrl
in the
pulsar_metadata
section, you can specify the connection details for your metadata store, such as ZooKeeper, etcd, or another supported service. Here's an example using ZooKeeper:
Copy code
pulsar_metadata:
  configurationMetadataStoreUrl: "zk:my-zk-1:2181,my-zk-2:2181,my-zk-3:2181"
In this example, replace
my-zk-1
,
my-zk-2
, and
my-zk-3
with the hostnames or IP addresses of your ZooKeeper nodes, and
2181
with the port number if it's different from the default. Would you like more detailed guidance? Sources: - https://github.com/apache/pulsar/blob/master/pulsar-broker/src/test/java/org/apache/pulsar/common/naming/ServiceConfigurationTest.java - https://github.com/apache/pulsar/issues/19920 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.