cli: can't use cockroach quit once quorum is lost
#1252
Assignees
Labels
Comments
jseldess
pushed a commit
that referenced
this issue
Apr 6, 2017
These changes attempt to keep the Start a Cluster tutorial quick and easy while introducing new users to what makes CockroachDB unique, not just ease of deployment, but also automated replication and survival. I've also stripped out some details that I think are not important to the majority of users getting up and running for the first time, e.g., how to customize `start` flags and the fact that you can use third-party monitoring. Finally, I've update the Stop the Cluster step to account for the fact that `cockroach quit` can't be used to stop nodes once quorum is lost. Fixes #1191 Fixes #1252
jseldess
pushed a commit
that referenced
this issue
Apr 6, 2017
These changes attempt to keep the Start a Cluster tutorial quick and easy while introducing new users to what makes CockroachDB unique, not just ease of deployment, but also automated replication and survival. I've also stripped out some details that I think are not important to the majority of users getting up and running for the first time, e.g., how to customize `start` flags and the fact that you can use third-party monitoring. Finally, I've update the Stop the Cluster step to account for the fact that `cockroach quit` can't be used to stop nodes once quorum is lost. Fixes #1191 Fixes #1252
jseldess
pushed a commit
that referenced
this issue
Apr 7, 2017
These changes attempt to keep the Start a Cluster tutorial quick and easy while introducing new users to what makes CockroachDB unique, not just ease of deployment, but also automated replication and survival. I've also stripped out some details that I think are not important to the majority of users getting up and running for the first time, e.g., how to customize `start` flags and the fact that you can use third-party monitoring. Finally, I've update the Stop the Cluster step to account for the fact that `cockroach quit` can't be used to stop nodes once quorum is lost. Fixes #1191 Fixes #1252
jseldess
pushed a commit
that referenced
this issue
Apr 7, 2017
These changes attempt to keep the Start a Cluster tutorial quick and easy while introducing new users to what makes CockroachDB unique, not just ease of deployment, but also automated replication and survival. I've also stripped out some details that I think are not important to the majority of users getting up and running for the first time, e.g., how to customize `start` flags and the fact that you can use third-party monitoring. Finally, I've update the Stop the Cluster step to account for the fact that `cockroach quit` can't be used to stop nodes once quorum is lost. Fixes #1191 Fixes #1252
jseldess
pushed a commit
that referenced
this issue
Apr 7, 2017
These changes attempt to keep the Start a Cluster tutorial quick and easy while introducing new users to what makes CockroachDB unique, not just ease of deployment, but also automated replication and survival. I've also stripped out some details that I think are not important to the majority of users getting up and running for the first time, e.g., how to customize `start` flags and the fact that you can use third-party monitoring. Finally, I've update the Stop the Cluster step to account for the fact that `cockroach quit` can't be used to stop nodes once quorum is lost. Fixes #1191 Fixes #1252
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See cockroachdb/cockroach#14620 for details.
Need to update getting started docs. Also need to call this out in
cockroach quitdocs, though this shouldn't be as much an issue for production clusters, which will do rolling upgrades.The text was updated successfully, but these errors were encountered: