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

Production recommendation: include multiple node addresses in --join #739

Closed
jseldess opened this issue Oct 10, 2016 · 1 comment
Closed
Labels
O-external Origin: Issue comes from external users. T-enhancement X-duplicate

Comments

@jseldess
Copy link
Contributor

jseldess commented Oct 10, 2016

When adding a node to a cluster, you must specify the address of at least one existing node in the --join flag. We should update production deployment docs to recommend putting multiple node addresses in there, so the node can restart even if one of the nodes in join isn't available.

In local startup docs, probably ok to leave the code samples with one other address in join, but we could mention this in the supporting text.

Also, we should clarify that --join is not required on node restart. The only exception is if, when a node was started, it was shut down before it saved its peer address to disk.

@knz, @aphyr

@jseldess jseldess added T-enhancement O-external Origin: Issue comes from external users. labels Oct 10, 2016
@jseldess jseldess changed the title Production recommendation: include all node addresses in --join Production recommendation: include multiple node addresses in --join Oct 10, 2016
@jseldess
Copy link
Contributor Author

Closing in favor of #3395.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
O-external Origin: Issue comes from external users. T-enhancement X-duplicate
Projects
None yet
Development

No branches or pull requests

1 participant