[
https://issues.apache.org/jira/browse/CASSANDRA-8523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16146592#comment-16146592
]
ASF GitHub Bot commented on CASSANDRA-8523:
-------------------------------------------
GitHub user kgreav opened a pull request:
https://github.com/apache/cassandra/pull/145
Describe replacement cases based on CASSANDRA-8523 and CASSANDRA-12344
Just updating the docs to cover cases where replacing with a same IP node
and different IP node.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kgreav/cassandra replace_fix
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cassandra/pull/145.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #145
----
commit e9228182d7f6916eab0dd64afcc57fedb103f25c
Author: kurt <[email protected]>
Date: 2017-08-29T03:36:12Z
Describe replacement cases based on CASSANDRA-8523 and CASSANDRA-12344
----
> Writes should be sent to a replacement node while it is streaming in data
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-8523
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8523
> Project: Cassandra
> Issue Type: Bug
> Reporter: Richard Wagner
> Assignee: Paulo Motta
> Fix For: 2.2.8, 3.0.9, 3.10
>
>
> In our operations, we make heavy use of replace_address (or
> replace_address_first_boot) in order to replace broken nodes. We now realize
> that writes are not sent to the replacement nodes while they are in hibernate
> state and streaming in data. This runs counter to what our expectations were,
> especially since we know that writes ARE sent to nodes when they are
> bootstrapped into the ring.
> It seems like cassandra should arrange to send writes to a node that is in
> the process of replacing another node, just like it does for a nodes that are
> bootstraping. I hesitate to phrase this as "we should send writes to a node
> in hibernate" because the concept of hibernate may be useful in other
> contexts, as per CASSANDRA-8336. Maybe a new state is needed here?
> Among other things, the fact that we don't get writes during this period
> makes subsequent repairs more expensive, proportional to the number of writes
> that we miss (and depending on the amount of data that needs to be streamed
> during replacement and the time it may take to rebuild secondary indexes, we
> could miss many many hours worth of writes). It also leaves us more exposed
> to consistency violations.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
