You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(see travis config in job history, the difference is just the param -Dswarm-bind-method=member-address-provider)
Failure (sample extract below, there are no logs showing "Accepting socket connections") and member list is just ONE, (should be 10, the cluster never fully joins up) (see travis logs above)
Dec 14, 2017 8:17:07 PM com.hazelcast.nio.tcp.TcpIpConnectionManager
INFO: [10.0.0.8]:5701 [hazelcast-docker-swarm-discovery-spi] [3.9.1] Established socket connection between /10.0.0.8:34369 and /10.0.0.12:5701
Dec 14, 2017 8:17:07 PM com.hazelcast.nio.tcp.TcpIpConnectionManager
INFO: [10.0.0.8]:5701 [hazelcast-docker-swarm-discovery-spi] [3.9.1] Established socket connection between /10.0.0.8:33002 and /10.0.0.3:5701
Dec 14, 2017 8:17:07 PM com.hazelcast.nio.tcp.TcpIpConnectionManager
INFO: [10.0.0.8]:5701 [hazelcast-docker-swarm-discovery-spi] [3.9.1] Established socket connection between /10.0.0.8:51974 and /10.0.0.6:5701
The only real difference between these examples is the use of a custom AddressPicker (which works) vs using the new MemberAddressProvider SPI which was introduced to avoid the AddressPicker hack.
@bitsofinfo Seems like there is a problem in SwarmMemberAddressProvider, while constructing its SwarmDiscoveryUtil instance it passes bindSocketChannel = true to the constructor, but MemberAddressProviders are not responsible for socket creation/binding. This effectively blocks HZ from binding its own socket to the address, please try passing bindSocketChannel = false.
bitsofinfo
added a commit
to bitsofinfo/hazelcast-docker-swarm-discovery-spi
that referenced
this issue
Dec 27, 2017
I'm attempting to upgrade https://github.com/bitsofinfo/hazelcast-docker-swarm-discovery-spi to leverage the new
MemberAddressProvider
SPI (#11548)Current working swarm discovery spi works fine w/ custom AddressPicker
The current working version of the swarm discovery strategy relies on defining a custom
AddressPicker
. This works fine w/ hazelcast 3.8 and 3.9.x (RC3) https://github.com/bitsofinfo/hazelcast-docker-swarm-discovery-spi/tree/1.0-RC3Results against HZ 3.9.1 with a custom
AddressPicker
implementation: https://travis-ci.org/bitsofinfo/hazelcast-docker-swarm-discovery-spi/jobs/316600832(see travis config in job history, the difference is just the param
-Dswarm-bind-method=address-picker
)Indications of successful cluster formation (sample extract below) + member list is accurate (see travis logs above)
Pending version of swarm discovery spi with MemberAddressProvider SPI solution fails
The MASTER branch has been updated for hazelcast 3.9.x and provides a
SwarmMemberAddressProvider
https://github.com/bitsofinfo/hazelcast-docker-swarm-discovery-spi/blob/master/src/main/java/org/bitsofinfo/hazelcast/discovery/docker/swarm/SwarmMemberAddressProvider.java
However when this is used everything is discovered fine by the discovery code, however hazelcast never forms a cluster
Results when the new
MemberAddressProvider
SPI is used:https://travis-ci.org/bitsofinfo/hazelcast-docker-swarm-discovery-spi/jobs/316603960
(see travis config in job history, the difference is just the param
-Dswarm-bind-method=member-address-provider
)Failure (sample extract below, there are no logs showing "Accepting socket connections") and member list is just ONE, (should be 10, the cluster never fully joins up) (see travis logs above)
The only real difference between these examples is the use of a custom
AddressPicker
(which works) vs using the newMemberAddressProvider
SPI which was introduced to avoid theAddressPicker
hack.Configs used by the test operating in either mode are here:
https://github.com/bitsofinfo/hazelcast-docker-swarm-discovery-spi/tree/master/src/main/resources
https://github.com/bitsofinfo/hazelcast-docker-swarm-discovery-spi/blob/master/src/main/java/org/bitsofinfo/hazelcast/discovery/docker/swarm/test/DockerTestRunner.java
The text was updated successfully, but these errors were encountered: