Causal clustering is not configurable with Docker service name (swarm mode) about docker-neo4j HOT 5 CLOSED

Even better would be to support dynamic (broadcast or something) initial members discovery (to free people from configuring that by hand when it's not strictly needed), something that proves to be very inconvenient on ECS.

from docker-neo4j.

@jarellm were you able to find a solution to this issue? I'm currently experimenting with swarm and running into the same problem.

from docker-neo4j.

From the next released version >= 3.2 (i.e. 3.2.3 when it's released) we will have support for putting a DNS name as your discovery member. neo4j/neo4j#9655

We still need to add an environment variable to the Docker entry point script so you can control the discovery mode.

from docker-neo4j.

@jarellm I think the drivers already support DNS lookup but I'm not sure what version that was introduced. Maybe try out the 1.4 series - I'm pretty sure it's implemented in there.

from docker-neo4j.

@albert-the-creator, I settled for the workaround I provided since we won't be scaling the service any time soon anyway. But it seems that this has been solved in v3.2 as stated by @mneedham

hey @mneedham not sure if you're referring to the bolt+routing protocol, but I got no issues re:
neo4j client -[bolt+routing]->causal cluster

My issue was during discovery part of the core servers which I think is solved by the pull request. Creating a custom Docker image to add this will work for now.

Many thanks!

from docker-neo4j.