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

Multi-node Cluster Issue #6520

Open
tarpanpathak opened this issue Oct 10, 2017 · 2 comments
Open

Multi-node Cluster Issue #6520

tarpanpathak opened this issue Oct 10, 2017 · 2 comments
Labels
Milestone

Comments

@tarpanpathak
Copy link

I'm using Nomad to deploy a cluster of rethinkdb containers. I tried several different Docker images and Nomad configs but each container comes up as a leader and never joins the cluster/leader. The logs do NOT hint at why so any help would be greatly appreciated. Let me know if more information is required to reproduce this.

@srh srh added this to the question milestone Nov 16, 2017
@srh
Copy link
Contributor

srh commented Nov 16, 2017

I think seeing the command lines used to launch the RethinkDB instances is the first piece of information needed.

@tarpanpathak
Copy link
Author

Tried two different approaches but get the same result.

Method 1: Brought up the leader using the first command and the followers using the second:

command = "rethinkdb"
args = [ "--bind", "all" ]
command = "rethinkdb"
args = [ "--bind", "all", "-j", "leader_ip:port"]

Method 2: Brought up all containers (through Nomad) at the same time using:

command = "rethinkdb"
args = [ "--bind", "all", "-j", "${NOMAD_TASK_NAME}-0"] # Uses an alias that is `query-able' across containers

Let me know if you need more info.

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

No branches or pull requests

3 participants