pods for broker/bookkeeper init failed - Could not find or load main class "-Xms1g error about pulsar-helm-chart HOT 8 CLOSED

@rvashishth please use the latest master to include #24

from pulsar-helm-chart.

@rvashishth Are you running with the latest master?

from pulsar-helm-chart.

I don't see -Xms1g in the default vaules.ymal file. Can you share your values file?

from pulsar-helm-chart.

@sijie I used this Values.yml file from from the previous commit after PR #22 merged. I didn't make any changes in this values file.

looks like some config issue at bkEnv.sh

This error looks somewhat similar to these two issues - apache/pulsar#7243, or apache/pulsar#6355

from pulsar-helm-chart.

@sijie I have tested with the latest master with #28, still the same error with init containers.

from pulsar-helm-chart.

this time zookeeper also going in CrashLoopBackOff status with the below error.

$ kubectl logs pulsar-zookeeper-0  -n pulsar
[conf/zookeeper.conf] Applying config dataDir = /pulsar/data/zookeeper
[conf/zookeeper.conf] Adding config serverCnxnFactory = org.apache.zookeeper.server.NettyServerCnxnFactory
Current server id 1
Error: Could not find or load main class "-Xms1g

from pulsar-helm-chart.

Similar, I'm trying the latest master and my bookies are now failing to start with:

Error: Could not find or load main class "
JMX enabled by default

from pulsar-helm-chart.

all pods started successfully. the previous issue was due to chart being cached.

from pulsar-helm-chart.