Skip to content

Conversation

jgardiner68
Copy link
Contributor

This needs testing

  • More details on the docker network
  • added port info to the members
  • added a docker name to make these easier to identify within docker
  • enabled CLC/Console in both
  • More instructions on IP addresses (more details in the logged info)
  • changed the startup docker command for tokyo cluster as the paths were not working
  • added an example using CLC to check the data on the passive cluster
  • clean up instructions on how to remove the docker network

* More details on the docker network
* added port info to the members
* added a docker name to make these easier to identify within docker
* enabled CLC/Console in both
* More instructions on IP addresses (more details in the logged info)
* changed the startup docker command for tokyo cluster as the paths were not working
* added an example using CLC to check the data on the passive cluster
* clean up instructions on how to remove the docker network
@jgardiner68 jgardiner68 requested a review from a team as a code owner August 19, 2025 21:03
Copy link

netlify bot commented Aug 19, 2025

Deploy Preview for hardcore-allen-f5257d ready!

Name Link
🔨 Latest commit dd1b421
🔍 Latest deploy log https://app.netlify.com/projects/hardcore-allen-f5257d/deploys/68a4e6a0536d810008c3786b
😎 Deploy Preview https://deploy-preview-1836--hardcore-allen-f5257d.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

docker run \
-p 5701:5701 \
--name hazelcast-london \
--network hazelcast-network \
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove to avoid container name clashes

docker run \
--network hazelcast-network \
-e JAVA_OPTS="-Dhazelcast.config=/opt/hazelcast/config_ext/hazelcast.yaml" -v ~/config-tokyo:/opt/hazelcast/config_ext hazelcast/hazelcast-enterprise:{ee-version}
--name hazelcast-tokyo \
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove to avoid container name clashes

@oliverhowell oliverhowell self-assigned this Aug 20, 2025
@jgardiner68
Copy link
Contributor Author

@oliverhowell Is this PR now out of date?

@oliverhowell
Copy link
Contributor

@oliverhowell Is this PR now out of date?

It was always going to clash with #1784 anyway but I've pulled the changes in so it's fine. I'll close this when I merge my master PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants