You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Anthony Molinaro (JIRA)" <ji...@apache.org> on 2009/11/19 20:33:39 UTC
[jira] Created: (CASSANDRA-564) Provide recoverability when a node
dies and it is impossible to get the same IP.
Provide recoverability when a node dies and it is impossible to get the same IP.
--------------------------------------------------------------------------------
Key: CASSANDRA-564
URL: https://issues.apache.org/jira/browse/CASSANDRA-564
Project: Cassandra
Issue Type: Improvement
Components: Core
Affects Versions: 0.4, 0.5
Reporter: Anthony Molinaro
>From the descriptions on the mailing list, when a node dies permanently from hardware or other failure and you need to replace it, it must have the same IP. For people running in cloud environments, this is often times impossible. So it would be very useful if there was a way to replace a node with a new node without requiring the same IP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CASSANDRA-564) Provide recoverability when a node
dies and it is impossible to get the same IP.
Posted by "Jaakko Laine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jaakko Laine updated CASSANDRA-564:
-----------------------------------
Attachment: (was: 564a.patch)
> Provide recoverability when a node dies and it is impossible to get the same IP.
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-564
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Anthony Molinaro
> Priority: Minor
> Fix For: 0.5
>
>
> From the descriptions on the mailing list, when a node dies permanently from hardware or other failure and you need to replace it, it must have the same IP. For people running in cloud environments, this is often times impossible. So it would be very useful if there was a way to replace a node with a new node without requiring the same IP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-564) Provide recoverability when a
node dies and it is impossible to get the same IP.
Posted by "Jaakko Laine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785697#action_12785697 ]
Jaakko Laine commented on CASSANDRA-564:
----------------------------------------
Not directly related to this, but close anyway: Currently Gossiper will evict a node from membership if it has not heard anything from it for 3 days. At this stage the node is removed from gossiper's own data structures (unreachableEndpoints), but not from token metadata. Currently token metadata is never cleaned up unless the node is decommissioned, should we do that at some point, too?
Another thing is: when a node enters the ring (that is, broadcasts STATE_NORMAL), there is no check in token metadata or storage service to prevent another IP from taking a token. Token metadata is simply updated with the new endpoint/token information. From this it would seem that another node can take the same token.
>From this it would seem that this improvement request is to decommission a dead node from the ring? Replacing refers to taking the same token, but that would seem to be possible already.
> Provide recoverability when a node dies and it is impossible to get the same IP.
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-564
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Anthony Molinaro
> Priority: Minor
> Fix For: 0.5
>
>
> From the descriptions on the mailing list, when a node dies permanently from hardware or other failure and you need to replace it, it must have the same IP. For people running in cloud environments, this is often times impossible. So it would be very useful if there was a way to replace a node with a new node without requiring the same IP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-564) Provide recoverability when a
node dies and it is impossible to get the same IP.
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785710#action_12785710 ]
Jonathan Ellis commented on CASSANDRA-564:
------------------------------------------
> Currently Gossiper will evict a node from membership if it has not heard anything from it for 3 days
I'd rather have eviction/decomission entirely operator-controlled.
> this improvement requestis to decommission a dead node from the ring
yes.
> Provide recoverability when a node dies and it is impossible to get the same IP.
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-564
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Anthony Molinaro
> Priority: Minor
> Fix For: 0.5
>
>
> From the descriptions on the mailing list, when a node dies permanently from hardware or other failure and you need to replace it, it must have the same IP. For people running in cloud environments, this is often times impossible. So it would be very useful if there was a way to replace a node with a new node without requiring the same IP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CASSANDRA-564) Provide recoverability when a node
dies and it is impossible to get the same IP.
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-564:
-------------------------------------
Fix Version/s: 0.5
Priority: Minor (was: Major)
Affects Version/s: (was: 0.5)
(was: 0.4)
> Provide recoverability when a node dies and it is impossible to get the same IP.
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-564
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Anthony Molinaro
> Priority: Minor
> Fix For: 0.5
>
>
> From the descriptions on the mailing list, when a node dies permanently from hardware or other failure and you need to replace it, it must have the same IP. For people running in cloud environments, this is often times impossible. So it would be very useful if there was a way to replace a node with a new node without requiring the same IP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-564) Provide recoverability when a
node dies and it is impossible to get the same IP.
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789278#action_12789278 ]
Hudson commented on CASSANDRA-564:
----------------------------------
Integrated in Cassandra #284 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/284/])
> Provide recoverability when a node dies and it is impossible to get the same IP.
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-564
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Anthony Molinaro
> Assignee: Jaakko Laine
> Priority: Minor
> Fix For: 0.5
>
> Attachments: 564-1-replace-bootstrapmetadata-with-streamrequest.patch, 564-2-add-removetoken-command.patch
>
>
> From the descriptions on the mailing list, when a node dies permanently from hardware or other failure and you need to replace it, it must have the same IP. For people running in cloud environments, this is often times impossible. So it would be very useful if there was a way to replace a node with a new node without requiring the same IP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-564) Provide recoverability when a
node dies and it is impossible to get the same IP.
Posted by "Jaakko Laine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785782#action_12785782 ]
Jaakko Laine commented on CASSANDRA-564:
----------------------------------------
Difficult to say :)
I think version b is "cleaner", but then again if we decide to go for single state gossip (#572), then STATE_LEFT would become already a 3-tuple (is it triple?). No problem in this, though, just becomes a very long string :)
> Provide recoverability when a node dies and it is impossible to get the same IP.
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-564
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Anthony Molinaro
> Priority: Minor
> Fix For: 0.5
>
> Attachments: 564-2-fix-comment.patch, 564a.patch, 564b-use-tuple-state-left.patch
>
>
> From the descriptions on the mailing list, when a node dies permanently from hardware or other failure and you need to replace it, it must have the same IP. For people running in cloud environments, this is often times impossible. So it would be very useful if there was a way to replace a node with a new node without requiring the same IP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-564) Provide recoverability when a
node dies and it is impossible to get the same IP.
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785779#action_12785779 ]
Jonathan Ellis commented on CASSANDRA-564:
------------------------------------------
ack, 3 versions? which do you prefer? :)
> Provide recoverability when a node dies and it is impossible to get the same IP.
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-564
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Anthony Molinaro
> Priority: Minor
> Fix For: 0.5
>
> Attachments: 564-2-fix-comment.patch, 564a.patch, 564b-use-tuple-state-left.patch
>
>
> From the descriptions on the mailing list, when a node dies permanently from hardware or other failure and you need to replace it, it must have the same IP. For people running in cloud environments, this is often times impossible. So it would be very useful if there was a way to replace a node with a new node without requiring the same IP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-564) Provide recoverability when a
node dies and it is impossible to get the same IP.
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786179#action_12786179 ]
Jonathan Ellis commented on CASSANDRA-564:
------------------------------------------
I don't see where we do data transfers to move the right data to the node whose range expands by the dead node being removed, or updating other replicas now responsible for copies. We might need a new gossip state for that.
If that is done should we remove decommission as a redundant special case?
> Provide recoverability when a node dies and it is impossible to get the same IP.
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-564
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Anthony Molinaro
> Priority: Minor
> Fix For: 0.5
>
> Attachments: 564-2-fix-comment.patch, 564a.patch, 564b-use-tuple-state-left.patch
>
>
> From the descriptions on the mailing list, when a node dies permanently from hardware or other failure and you need to replace it, it must have the same IP. For people running in cloud environments, this is often times impossible. So it would be very useful if there was a way to replace a node with a new node without requiring the same IP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CASSANDRA-564) Provide recoverability when a node
dies and it is impossible to get the same IP.
Posted by "Jaakko Laine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jaakko Laine updated CASSANDRA-564:
-----------------------------------
Attachment: 564b-use-tuple-state-left.patch
564a.patch
For this issue I think there is no point going throug state leaving as that state is only for setting pending ranges. That is not very useful for a node that is already beyond repair, so simply broadcast STATE_LEFT to remove it from token metadata. The "cleanest" way would be to have separate state for this gossip, but that would add data to gossip just for this purpose, which is not very good option. Instead use STATE_LEFT with some small maneuvering in onChange.
Attached two alternative patches for this issue with slightly different approach:
564a: do not change current gossiping and just handle both normal leave and remove token commands in onChange.
564b: modify STATE_LEFT to a tuple (REMOVE_TOKEN|LEFT_NORMALLY),<token>. This gives small extra amount of safety as onChange can make extra checks based on what is supposed to be going on. This approach overlaps slightly with the discussion on issue #572 with regard state gossip format.
Both patches include small tweak to STATE_NORMAL handling code as well.
> Provide recoverability when a node dies and it is impossible to get the same IP.
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-564
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Anthony Molinaro
> Priority: Minor
> Fix For: 0.5
>
> Attachments: 564a.patch, 564b-use-tuple-state-left.patch
>
>
> From the descriptions on the mailing list, when a node dies permanently from hardware or other failure and you need to replace it, it must have the same IP. For people running in cloud environments, this is often times impossible. So it would be very useful if there was a way to replace a node with a new node without requiring the same IP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CASSANDRA-564) Provide recoverability when a node
dies and it is impossible to get the same IP.
Posted by "Jaakko Laine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jaakko Laine updated CASSANDRA-564:
-----------------------------------
Attachment: (was: 564b-use-tuple-state-left.patch)
> Provide recoverability when a node dies and it is impossible to get the same IP.
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-564
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Anthony Molinaro
> Priority: Minor
> Fix For: 0.5
>
>
> From the descriptions on the mailing list, when a node dies permanently from hardware or other failure and you need to replace it, it must have the same IP. For people running in cloud environments, this is often times impossible. So it would be very useful if there was a way to replace a node with a new node without requiring the same IP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-564) Provide recoverability when a
node dies and it is impossible to get the same IP.
Posted by "Jaakko Laine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786895#action_12786895 ]
Jaakko Laine commented on CASSANDRA-564:
----------------------------------------
Overlooked that part completely. I think we might be able to do this without a new Gossip state, but I'll have another look tomorrow when checking the pending range issue.
> Provide recoverability when a node dies and it is impossible to get the same IP.
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-564
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Anthony Molinaro
> Priority: Minor
> Fix For: 0.5
>
>
> From the descriptions on the mailing list, when a node dies permanently from hardware or other failure and you need to replace it, it must have the same IP. For people running in cloud environments, this is often times impossible. So it would be very useful if there was a way to replace a node with a new node without requiring the same IP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-564) Provide recoverability when a
node dies and it is impossible to get the same IP.
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786180#action_12786180 ]
Jonathan Ellis commented on CASSANDRA-564:
------------------------------------------
(I did commit the isClientMode simplification.)
> Provide recoverability when a node dies and it is impossible to get the same IP.
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-564
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Anthony Molinaro
> Priority: Minor
> Fix For: 0.5
>
> Attachments: 564-2-fix-comment.patch, 564a.patch, 564b-use-tuple-state-left.patch
>
>
> From the descriptions on the mailing list, when a node dies permanently from hardware or other failure and you need to replace it, it must have the same IP. For people running in cloud environments, this is often times impossible. So it would be very useful if there was a way to replace a node with a new node without requiring the same IP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CASSANDRA-564) Provide recoverability when a node
dies and it is impossible to get the same IP.
Posted by "Jaakko Laine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jaakko Laine updated CASSANDRA-564:
-----------------------------------
Attachment: 564-2-fix-comment.patch
fix wrong comment
> Provide recoverability when a node dies and it is impossible to get the same IP.
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-564
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Anthony Molinaro
> Priority: Minor
> Fix For: 0.5
>
> Attachments: 564-2-fix-comment.patch, 564a.patch, 564b-use-tuple-state-left.patch
>
>
> From the descriptions on the mailing list, when a node dies permanently from hardware or other failure and you need to replace it, it must have the same IP. For people running in cloud environments, this is often times impossible. So it would be very useful if there was a way to replace a node with a new node without requiring the same IP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-564) Provide recoverability when a
node dies and it is impossible to get the same IP.
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783826#action_12783826 ]
Jonathan Ellis commented on CASSANDRA-564:
------------------------------------------
IMO the right approach here is to have a JMX command telling it to trigger the decommission code for a node that is no longer alive to broadcast that cleanly.
> Provide recoverability when a node dies and it is impossible to get the same IP.
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-564
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Anthony Molinaro
> Priority: Minor
> Fix For: 0.5
>
>
> From the descriptions on the mailing list, when a node dies permanently from hardware or other failure and you need to replace it, it must have the same IP. For people running in cloud environments, this is often times impossible. So it would be very useful if there was a way to replace a node with a new node without requiring the same IP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-564) Provide recoverability when a
node dies and it is impossible to get the same IP.
Posted by "Jaakko Laine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787463#action_12787463 ]
Jaakko Laine commented on CASSANDRA-564:
----------------------------------------
I think we can do with existing STATE_LEFT gossip state, just use the kind of tuple mentioned earlier as an application state. If STATE_LEFT was a result of normal leave, just do the same thing as now. If it was a result of remove token command, the nodes affected by range changes, get the data from other replicas to restore replica count. Decommissioning could be left as it is, since it is a case of node gracefully leaving and handing over its data to other nodes. Remove token is to signal to other nodes that this node is no loger in service, so please restore replica count to what it should be.
This latter functionality could be used together with Gossiper to have the cluster automatically maintain replica count (automatically joust a node ouf ot cluster and restore replica count after certain period of time). Don't know if this kind of functionality would be needed, but having such self-repair would be nice at least on paper.
> Provide recoverability when a node dies and it is impossible to get the same IP.
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-564
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Anthony Molinaro
> Priority: Minor
> Fix For: 0.5
>
>
> From the descriptions on the mailing list, when a node dies permanently from hardware or other failure and you need to replace it, it must have the same IP. For people running in cloud environments, this is often times impossible. So it would be very useful if there was a way to replace a node with a new node without requiring the same IP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CASSANDRA-564) Provide recoverability when a node
dies and it is impossible to get the same IP.
Posted by "Jaakko Laine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jaakko Laine updated CASSANDRA-564:
-----------------------------------
Attachment: 564-2-add-removetoken-command.patch
564-1-replace-bootstrapmetadata-with-streamrequest.patch
New Version
564-1
- Rename BootstrapMetadata and friends to StreamRequest* as that is what those essentially are. Move them to cassandra.io where rest of streaming stuff resides.
- Remove some unneeded imports from BootStrapper
564-2
Add removeToken command and related stuff to StorageService. This now uses STATE_LEFT state, but we might also create another state for this, if needed.
> Provide recoverability when a node dies and it is impossible to get the same IP.
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-564
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Anthony Molinaro
> Priority: Minor
> Fix For: 0.5
>
> Attachments: 564-1-replace-bootstrapmetadata-with-streamrequest.patch, 564-2-add-removetoken-command.patch
>
>
> From the descriptions on the mailing list, when a node dies permanently from hardware or other failure and you need to replace it, it must have the same IP. For people running in cloud environments, this is often times impossible. So it would be very useful if there was a way to replace a node with a new node without requiring the same IP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CASSANDRA-564) Provide recoverability when a node
dies and it is impossible to get the same IP.
Posted by "Jaakko Laine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jaakko Laine updated CASSANDRA-564:
-----------------------------------
Attachment: (was: 564-2-fix-comment.patch)
> Provide recoverability when a node dies and it is impossible to get the same IP.
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-564
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Anthony Molinaro
> Priority: Minor
> Fix For: 0.5
>
>
> From the descriptions on the mailing list, when a node dies permanently from hardware or other failure and you need to replace it, it must have the same IP. For people running in cloud environments, this is often times impossible. So it would be very useful if there was a way to replace a node with a new node without requiring the same IP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CASSANDRA-564) Provide recoverability when a node
dies and it is impossible to get the same IP.
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-564.
--------------------------------------
Resolution: Fixed
Assignee: Jaakko Laine
committed
> Provide recoverability when a node dies and it is impossible to get the same IP.
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-564
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Anthony Molinaro
> Assignee: Jaakko Laine
> Priority: Minor
> Fix For: 0.5
>
> Attachments: 564-1-replace-bootstrapmetadata-with-streamrequest.patch, 564-2-add-removetoken-command.patch
>
>
> From the descriptions on the mailing list, when a node dies permanently from hardware or other failure and you need to replace it, it must have the same IP. For people running in cloud environments, this is often times impossible. So it would be very useful if there was a way to replace a node with a new node without requiring the same IP.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.