We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There's no quick and simple way to enable the CP subsystem when using the hazelcast chart.
hazelcast
Default is disabled; but there should be a one-liner to enable this so users can experiment with CP features.
The text was updated successfully, but these errors were encountered:
Hi @gbarnett-hz
Configuring hazelcast.yaml.hazelcast.cp-subsystem field in the values yaml file will actually enable cp subsystem.
hazelcast.yaml.hazelcast.cp-subsystem
e.g.
cluster: memberCount: 5 hazelcast: yaml: hazelcast: cp-subsystem: cp-member-count: 5 group-size: 3 session-time-to-live-seconds: 300 session-heartbeat-interval-seconds: 5 missing-cp-member-auto-removal-seconds: 14400 fail-on-indeterminate-operation-state: false
$ helm install hz hazelcast/hazelcast --values=values.yaml
Checking the logs one of the member:
2023-08-22 16:23:12,312 [ INFO] [main] [c.h.c.CPSubsystem]: [172.17.0.6]:5701 [dev] [5.3.1] CP Subsystem is enabled with 5 members.
Basically, the fields 'hazelcast.yaml' is used to configure hazelcast cluster members.
Sorry, something went wrong.
Ah, thanks!
As for one-line to enable cp-subsystem, you can run:
$ helm install hz hazelcast/hazelcast --set=hazelcast.yaml.hazelcast.cp-subsystem.cp-member-count=3
Closing per example by @semihbkgr
gbarnett-hz
Successfully merging a pull request may close this issue.
There's no quick and simple way to enable the CP subsystem when using the
hazelcast
chart.Default is disabled; but there should be a one-liner to enable this so users can experiment with CP features.
The text was updated successfully, but these errors were encountered: