Cassandra node self-removal
up vote
0
down vote
favorite
I run Cassandra 3.1 in autoscaling group. Recently one of the machines failed and got replaced. I did not lose any data, but client applications were trying to connect to a node which was marked down.
I am looking for a way to gracefully remove a node from a cluster with a quick command which I would invoke via systemd right before it shuts down cassandra during the shutdown process.
nodetool decommission involves data streaming and takes long time.
nodetool removenode and nodetool assassinate can't remove the node they are running at.
- Losing data is not my concern. My goal is fully automated node replacement.
- Fixing client libaries is out of scope of this question
cassandra
asked Nov 22 at 16:16
Volodymyr Linevych
911210
add a comment |
up vote
0
down vote
favorite
I run Cassandra 3.1 in autoscaling group. Recently one of the machines failed and got replaced. I did not lose any data, but client applications were trying to connect to a node which was marked down.
I am looking for a way to gracefully remove a node from a cluster with a quick command which I would invoke via systemd right before it shuts down cassandra during the shutdown process.
nodetool decommission involves data streaming and takes long time.
nodetool removenode and nodetool assassinate can't remove the node they are running at.
- Losing data is not my concern. My goal is fully automated node replacement.
- Fixing client libaries is out of scope of this question
cassandra
asked Nov 22 at 16:16
Volodymyr Linevych
911210
1
why not simply shutdown machine & call removenode from other?
– Alex Ott
Nov 22 at 16:42
1
Have you looked at the replace_address_first_boot method of replacing nodes? It doesn't cover use cases where you want to scale down (I'd go with Alex's suggestion for that, if you don't care about possibly losing data), but will be much more efficient in cases like the one you describe where the instance gets replaced. cassandra.apache.org/doc/latest/operating/…
– Justin Cameron
Nov 23 at 4:29
Thanks guys. @AlexOtt : that's what i'm doing right now and i am looking for a way to automate it
– Volodymyr Linevych
Nov 23 at 8:57
@JustinCameron In this case I have to know the address of a failed node before I start cassandra on a fresh machine. I will go with this option if I find no way to run "quickly deregister myself" command from a node that it being shut down.
– Volodymyr Linevych
Nov 23 at 9:00
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I run Cassandra 3.1 in autoscaling group. Recently one of the machines failed and got replaced. I did not lose any data, but client applications were trying to connect to a node which was marked down.
I am looking for a way to gracefully remove a node from a cluster with a quick command which I would invoke via systemd right before it shuts down cassandra during the shutdown process.
nodetool decommission involves data streaming and takes long time.
nodetool removenode and nodetool assassinate can't remove the node they are running at.
- Losing data is not my concern. My goal is fully automated node replacement.
- Fixing client libaries is out of scope of this question
cassandra
asked Nov 22 at 16:16
Volodymyr Linevych
911210
I run Cassandra 3.1 in autoscaling group. Recently one of the machines failed and got replaced. I did not lose any data, but client applications were trying to connect to a node which was marked down.
I am looking for a way to gracefully remove a node from a cluster with a quick command which I would invoke via systemd right before it shuts down cassandra during the shutdown process.
nodetool decommission involves data streaming and takes long time.
nodetool removenode and nodetool assassinate can't remove the node they are running at.
- Losing data is not my concern. My goal is fully automated node replacement.
- Fixing client libaries is out of scope of this question
cassandra
cassandra
asked Nov 22 at 16:16
Volodymyr Linevych
911210
asked Nov 22 at 16:16
Volodymyr Linevych
911210
asked Nov 22 at 16:16
Volodymyr Linevych
911210
asked Nov 22 at 16:16
Volodymyr Linevych
911210
asked Nov 22 at 16:16
Volodymyr Linevych
911210
911210
1
why not simply shutdown machine & call removenode from other?
– Alex Ott
Nov 22 at 16:42
1
Have you looked at the replace_address_first_boot method of replacing nodes? It doesn't cover use cases where you want to scale down (I'd go with Alex's suggestion for that, if you don't care about possibly losing data), but will be much more efficient in cases like the one you describe where the instance gets replaced. cassandra.apache.org/doc/latest/operating/…
– Justin Cameron
Nov 23 at 4:29
Thanks guys. @AlexOtt : that's what i'm doing right now and i am looking for a way to automate it
– Volodymyr Linevych
Nov 23 at 8:57
@JustinCameron In this case I have to know the address of a failed node before I start cassandra on a fresh machine. I will go with this option if I find no way to run "quickly deregister myself" command from a node that it being shut down.
– Volodymyr Linevych
Nov 23 at 9:00
add a comment |
1
why not simply shutdown machine & call removenode from other?
– Alex Ott
Nov 22 at 16:42
1
Have you looked at the replace_address_first_boot method of replacing nodes? It doesn't cover use cases where you want to scale down (I'd go with Alex's suggestion for that, if you don't care about possibly losing data), but will be much more efficient in cases like the one you describe where the instance gets replaced. cassandra.apache.org/doc/latest/operating/…
– Justin Cameron
Nov 23 at 4:29
Thanks guys. @AlexOtt : that's what i'm doing right now and i am looking for a way to automate it
– Volodymyr Linevych
Nov 23 at 8:57
@JustinCameron In this case I have to know the address of a failed node before I start cassandra on a fresh machine. I will go with this option if I find no way to run "quickly deregister myself" command from a node that it being shut down.
– Volodymyr Linevych
Nov 23 at 9:00
1
1
why not simply shutdown machine & call removenode from other?
– Alex Ott
Nov 22 at 16:42
why not simply shutdown machine & call removenode from other?
– Alex Ott
Nov 22 at 16:42
1
1
Have you looked at the replace_address_first_boot method of replacing nodes? It doesn't cover use cases where you want to scale down (I'd go with Alex's suggestion for that, if you don't care about possibly losing data), but will be much more efficient in cases like the one you describe where the instance gets replaced. cassandra.apache.org/doc/latest/operating/…
– Justin Cameron
Nov 23 at 4:29
Have you looked at the replace_address_first_boot method of replacing nodes? It doesn't cover use cases where you want to scale down (I'd go with Alex's suggestion for that, if you don't care about possibly losing data), but will be much more efficient in cases like the one you describe where the instance gets replaced. cassandra.apache.org/doc/latest/operating/…
– Justin Cameron
Nov 23 at 4:29
Thanks guys. @AlexOtt : that's what i'm doing right now and i am looking for a way to automate it
– Volodymyr Linevych
Nov 23 at 8:57
Thanks guys. @AlexOtt : that's what i'm doing right now and i am looking for a way to automate it
– Volodymyr Linevych
Nov 23 at 8:57
@JustinCameron In this case I have to know the address of a failed node before I start cassandra on a fresh machine. I will go with this option if I find no way to run "quickly deregister myself" command from a node that it being shut down.
– Volodymyr Linevych
Nov 23 at 9:00
@JustinCameron In this case I have to know the address of a failed node before I start cassandra on a fresh machine. I will go with this option if I find no way to run "quickly deregister myself" command from a node that it being shut down.
– Volodymyr Linevych
Nov 23 at 9:00
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53434883%2fcassandra-node-self-removal%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
why not simply shutdown machine & call removenode from other?
– Alex Ott
Nov 22 at 16:42
1
Have you looked at the replace_address_first_boot method of replacing nodes? It doesn't cover use cases where you want to scale down (I'd go with Alex's suggestion for that, if you don't care about possibly losing data), but will be much more efficient in cases like the one you describe where the instance gets replaced. cassandra.apache.org/doc/latest/operating/…
– Justin Cameron
Nov 23 at 4:29
Thanks guys. @AlexOtt : that's what i'm doing right now and i am looking for a way to automate it
– Volodymyr Linevych
Nov 23 at 8:57
@JustinCameron In this case I have to know the address of a failed node before I start cassandra on a fresh machine. I will go with this option if I find no way to run "quickly deregister myself" command from a node that it being shut down.
– Volodymyr Linevych
Nov 23 at 9:00