[
https://issues.apache.org/jira/browse/CASSANDRA-8193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216654#comment-14216654
]
Yuki Morishita commented on CASSANDRA-8193:
-------------------------------------------
Patch LGTM, with one thing.
We don't want to change StorageServiceMBean API at this point in 2.0, so can
you instead add new methods?
I know it looks redundant, but we will get rid of those in 3.0(trunk).
bq. It's getting quite ugly. nodetool only uses two of them...
Yeah, though there may be someone in the world using them outside of nodetool,
since those are just JMX interface.
Thus, we don't want to break API.
> Multi-DC parallel snapshot repair
> ---------------------------------
>
> Key: CASSANDRA-8193
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8193
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jimmy Mårdell
> Assignee: Jimmy Mårdell
> Priority: Minor
> Fix For: 2.0.12
>
> Attachments: cassandra-2.0-8193-1.txt, cassandra-2.0-8193-2.txt
>
>
> The current behaviour of snapshot repair is to let one node at a time
> calculate a merkle tree. This is to ensure only one node at a time is doing
> the expensive calculation. The drawback is that it takes even longer time to
> do the merkle tree calculation.
> In a multi-DC setup, I think it would make more sense to have one node in
> each DC calculate the merkle tree at the same time. This would yield a
> significant improvement when you have many data centers.
> I'm not sure how relevant this is in 2.1, but I don't see us upgrading to 2.1
> any time soon. Unless there is an obvious drawback that I'm missing, I'd like
> to implement this in the 2.0 branch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
