Skip to content
New issue

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

JGROUPS_DISCOVERY_EXTERNAL_IP to be set dynamically #13

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

michimau
Copy link

@michimau michimau commented May 5, 2022

@ivangfr, i took inspiration from your valuable work.

I work with an orchestrator, and I cannot manually set the JGROUPS_DISCOVERY_EXTERNAL_IP,
as I do not know the ip address of the container nor on which host it will land during the orchestrations.

The simple modification sets up JGROUPS_DISCOVERY_EXTERNAL_IP upon the output provided by the command "hostname -i".

Best
/michimau

Mauro Michielon added 2 commits May 5, 2022 16:52
to dynamically set JGROUPS_DISCOVERY_EXTERNAL_IP upon the container start.
@alejandroalffer
Copy link

alejandroalffer commented Jun 14, 2023

Please, consider follow the documentation https://infinispan.org/docs/stable/titles/server/server.html in order to understand the services needed for infinispan:

  • Al first, you need that each node has a static IP to bind the port. Keep in mind that using 127.0.0.1 will NOT expose the service to other nodes and you should use the IP LAN.
  • Notice that you also need two open ports to keep the active-active cluster: tcp/57800 and tcp/7800. In case your nodes run in the same network segment, you can use a udp-autodiscover function

The first node in the startup process will be the master. This startup process provides all the information you need in case of troubles.

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