Switch to use NODE_OPS_CMD for bootstrap operation #8472
Comments
asias
added a commit
to asias/scylla
that referenced
this issue
Apr 14, 2021
In commit 323f72e (repair: Switch to use NODE_OPS_CMD for replace operation), we switched replace operation to use the new NODE_OPS_CMD infrastructure. In this patch, we continue the work to switch bootstrap operation to use NODE_OPS_CMD. The benefits: - It is more reliable to detect pending node operations, to avoid multiple topology changes at the same time, than using gossip status. - The cluster reverts to a state before the bootstrap operation automatically in case of error much faster than gossip. - Allows users to pass a list of dead nodes to ignore during bootstrap explicitly. - The BOOTSTRAP gossip status is not needed any more. This is one step closer to achieve gossip-less topology change. Fixes scylladb#8472
asias
added a commit
to asias/scylla
that referenced
this issue
Apr 21, 2021
In commit 323f72e (repair: Switch to use NODE_OPS_CMD for replace operation), we switched replace operation to use the new NODE_OPS_CMD infrastructure. In this patch, we continue the work to switch bootstrap operation to use NODE_OPS_CMD. The benefits: - It is more reliable to detect pending node operations, to avoid multiple topology changes at the same time, than using gossip status. - The cluster reverts to a state before the bootstrap operation automatically in case of error much faster than gossip. - Allows users to pass a list of dead nodes to ignore during bootstrap explicitly. - The BOOTSTRAP gossip status is not needed any more. This is one step closer to achieve gossip-less topology change. Fixes scylladb#8472
asias
added a commit
to asias/scylla
that referenced
this issue
Apr 21, 2021
In commit 323f72e (repair: Switch to use NODE_OPS_CMD for replace operation), we switched replace operation to use the new NODE_OPS_CMD infrastructure. In this patch, we continue the work to switch bootstrap operation to use NODE_OPS_CMD. The benefits: - It is more reliable to detect pending node operations, to avoid multiple topology changes at the same time, than using gossip status. - The cluster reverts to a state before the bootstrap operation automatically in case of error much faster than gossip. - Allows users to pass a list of dead nodes to ignore during bootstrap explicitly. - The BOOTSTRAP gossip status is not needed any more. This is one step closer to achieve gossip-less topology change. Fixes scylladb#8472
asias
added a commit
to asias/scylla
that referenced
this issue
Apr 28, 2021
In commit 323f72e (repair: Switch to use NODE_OPS_CMD for replace operation), we switched replace operation to use the new NODE_OPS_CMD infrastructure. In this patch, we continue the work to switch bootstrap operation to use NODE_OPS_CMD. The benefits: - It is more reliable to detect pending node operations, to avoid multiple topology changes at the same time, than using gossip status. - The cluster reverts to a state before the bootstrap operation automatically in case of error much faster than gossip. - Allows users to pass a list of dead nodes to ignore during bootstrap explicitly. - The BOOTSTRAP gossip status is not needed any more. This is one step closer to achieve gossip-less topology change. Fixes scylladb#8472
avikivity
added a commit
that referenced
this issue
May 6, 2021
…ation' from Asias He In commit 323f72e (repair: Switch to use NODE_OPS_CMD for replace operation), we switched replace operation to use the new NODE_OPS_CMD infrastructure. In this patch set, we continue the work to switch decommission and bootstrap operation to use NODE_OPS_CMD. Fixes #8472 Fixes #8471 Closes #8481 * github.com:scylladb/scylla: repair: Switch to use NODE_OPS_CMD for bootstrap operation repair: Switch to use NODE_OPS_CMD for decommission operation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In commit 323f72e (repair: Switch to
use NODE_OPS_CMD for replace operation), we switched replace operation
to use the new NODE_OPS_CMD infrastructure.
We should continue to switch bootstrap operation to use
NODE_OPS_CMD.
The benefits:
It is more reliable to detect pending node operations, to avoid
multiple topology changes at the same time, than using gossip status.
The cluster reverts to a state before the bootstrap operation
automatically in case of error much faster than gossip.
Allows users to pass a list of dead nodes to ignore during bootstrap
explicitly.
The BOOTSTRAP gossip status is not needed any more. This is one step
closer to achieve gossip-less topology change.
The text was updated successfully, but these errors were encountered: