-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[docker] hazelcast into docker swarm, Virtual IP problem #9963
Comments
I temporary fix with custom discovery strategy using swarm API and SimpleDiscoveryNode with only virtual IP (without host name)
It is working perfectly!!!! |
I have the same problem. |
Try: https://github.com/bitsofinfo/hazelcast-docker-swarm-discovery-spi and see the SwarmAddressPicker |
Adds a new SPI for defining the addresses that the hazelcast instance will bind to and the address which will be advertised to other members on which they can bind to. This SPI will allow for implementations for different environments in which the default address picker does not pick suitable addresses and manually configuring the public address provides additional complexity for deploying hazelcast. The SPI does not necessarily fix all current issues when deploying hazelcast but provides the user with a way to avoid these issues by either providing their own implementation or using some implementation that hazelcast will provide in the future. Related to: hazelcast#10477 hazelcast#9963 hazelcast#11118
Adds a new SPI for defining the addresses that the hazelcast instance will bind to and the address which will be advertised to other members on which they can bind to. This SPI will allow for implementations for different environments in which the default address picker does not pick suitable addresses and manually configuring the public address provides additional complexity for deploying hazelcast. The SPI does not necessarily fix all current issues when deploying hazelcast but provides the user with a way to avoid these issues by either providing their own implementation or using some implementation that hazelcast will provide in the future. Related to: hazelcast#10477 hazelcast#9963 hazelcast#11118
Adds a new SPI for defining the addresses that the hazelcast instance will bind to and the address which will be advertised to other members on which they can bind to. This SPI will allow for implementations for different environments in which the default address picker does not pick suitable addresses and manually configuring the public address provides additional complexity for deploying hazelcast. The SPI does not necessarily fix all current issues when deploying hazelcast but provides the user with a way to avoid these issues by either providing their own implementation or using some implementation that hazelcast will provide in the future. Related to: hazelcast#10477 hazelcast#9963 hazelcast#11118
Adds a new SPI for defining the addresses that the hazelcast instance will bind to and the address which will be advertised to other members on which they can bind to. This SPI will allow for implementations for different environments in which the default address picker does not pick suitable addresses and manually configuring the public address provides additional complexity for deploying hazelcast. The SPI does not necessarily fix all current issues when deploying hazelcast but provides the user with a way to avoid these issues by either providing their own implementation or using some implementation that hazelcast will provide in the future. Related to: hazelcast#10477 hazelcast#9963 hazelcast#11118
Adds a new SPI for defining the addresses that the hazelcast instance will bind to and the address which will be advertised to other members on which they can bind to. This SPI will allow for implementations for different environments in which the default address picker does not pick suitable addresses and manually configuring the public address provides additional complexity for deploying hazelcast. The SPI does not necessarily fix all current issues when deploying hazelcast but provides the user with a way to avoid these issues by either providing their own implementation or using some implementation that hazelcast will provide in the future. Related to: hazelcast#10477 hazelcast#9963 hazelcast#11118
Adds a new SPI for defining the addresses that the hazelcast instance will bind to and the address which will be advertised to other members on which they can bind to. This SPI will allow for implementations for different environments in which the default address picker does not pick suitable addresses and manually configuring the public address provides additional complexity for deploying hazelcast. The SPI does not necessarily fix all current issues when deploying hazelcast but provides the user with a way to avoid these issues by either providing their own implementation or using some implementation that hazelcast will provide in the future. Related to: hazelcast#10477 hazelcast#9963 hazelcast#11118
Adds a new SPI for defining the addresses that the hazelcast instance will bind to and the address which will be advertised to other members on which they can bind to. This SPI will allow for implementations for different environments in which the default address picker does not pick suitable addresses and manually configuring the public address provides additional complexity for deploying hazelcast. The SPI does not necessarily fix all current issues when deploying hazelcast but provides the user with a way to avoid these issues by either providing their own implementation or using some implementation that hazelcast will provide in the future. Related to: hazelcast#10477 hazelcast#9963 hazelcast#11118
Adds a new SPI for defining the addresses that the hazelcast instance will bind to and the address which will be advertised to other members on which they can bind to. This SPI will allow for implementations for different environments in which the default address picker does not pick suitable addresses and manually configuring the public address provides additional complexity for deploying hazelcast. The SPI does not necessarily fix all current issues when deploying hazelcast but provides the user with a way to avoid these issues by either providing their own implementation or using some implementation that hazelcast will provide in the future. Related to: hazelcast#10477 hazelcast#9963 hazelcast#11118
@Fabryprog @lokinell @bitsofinfo |
related: #10801 |
Hello,
i using hazelcast (tcp discovery) into a docker swarm cluster.
According to official documentation (https://docs.docker.com/engine/swarm/networking/) swarm assign a VIP and a "fisical" IP for every service.
When a hazelcast member try to connect to another i have a conflict IP because hazelcast match any service with 2 different IP (VIP and IP)
How to resolve it?
The text was updated successfully, but these errors were encountered: