Helm chart & developer profile

Hello,
When I install the helm chart with a developer profile by setting clusterSize, partitionCount & replicationFactor to 1, the broker pod fails to run with a configuration error.

Caused by: java.util.concurrent.CompletionException: java.lang.IllegalStateException: Expected that persisted cluster size ‘3’ is equal to given one ‘1’, but was different. Persisted configuration ‘Configuration{index=0, time=2021-10-21 03:25:51,286, members=[DefaultRaftMember{id=2, type=ACTIVE, updated=2021-10-21T15:25:51.286Z}, DefaultRaftMember{id=1, type=ACTIVE, updated=2021-10-21T15:25:51.286Z}, DefaultRaftMember{id=0, type=ACTIVE, updated=2021-10-21T15:25:51.286Z}]}’ is different then given one, new given member id’s are: ‘[0]’. Changing the configuration is not supported. Please restart with the same configuration or recreate a new cluster after deleting persisted data.
at java.util.concurrent.CompletableFuture.encodeThrowable(Unknown Source) ~[?:?]
at java.util.concurrent.CompletableFuture.completeThrowable(Unknown Source) ~[?:?]
at java.util.concurrent.CompletableFuture$UniCompose.tryFire(Unknown Source) ~[?:?]

Below are the profile values.

zeebe-cluster-helm:
clusterSize: 1
partitionCount: 1
replicationFactor: 1
pvcSize: “1Gi”
elasticsearch:
imageTag: 7.13.4
replicas: 1
minimumMasterNodes: 1

Any suggestions on what configuration is going wrong?

Using zeebe-full-helm-1.2.0

TIA

Hey @Siva

it looks like you have installed before a helm release in you cluster and the old configuration is still persisted. Be aware if you uninstall a helm release the PVC’s still exist, you have to clean them up (delete them) in order to start fresh.

Hope this helps.

Greets
Chris