[
https://issues.apache.org/jira/browse/CASSANDRA-9876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Geoffrey Yu updated CASSANDRA-9876:
-----------------------------------
Attachment: 9876-trunk.txt
I've attached a patch that should add in what is described in the ticket.
Specifically, it adds a new option {{--pull-repair}} to {{nodetool repair}}
that can be used as follows:
{{nodetool repair --in-hosts <host1>,<host2> --start-token <start> --end-token
<end> --pull-repair}}
Suppose {{<host1>}} is the node where the command is being run. Then
{{<host1>}} will only request data from {{<host2>}} during the streaming step
(if there is a mismatch) but will not send any data to {{<host2>}}.
The node where the command is being run must one of the two nodes specified by
{{--in-hosts}}. And of course the token range specified must be a range that
both nodes own.
> One way targeted repair
> -----------------------
>
> Key: CASSANDRA-9876
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9876
> Project: Cassandra
> Issue Type: Improvement
> Reporter: sankalp kohli
> Assignee: Geoffrey Yu
> Priority: Minor
> Attachments: 9876-trunk.txt
>
>
> Many applications use C* by writing to one local DC. The other DC is used
> when the local DC is unavailable. When the local DC becomes available, we
> want to run a targeted repair b/w one endpoint from each DC to minimize the
> data transfer over WAN. In this case, it will be helpful to do a one way
> repair in which data will only be streamed from other DC to local DC instead
> of streaming the data both ways. This will further minimize the traffic over
> WAN. This feature should only be supported if a targeted repair is run
> involving 2 hosts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
