You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Marcus Eriksson (JIRA)" <ji...@apache.org> on 2014/12/01 16:03:13 UTC
[jira] [Commented] (CASSANDRA-8267) Only stream from unrepaired
sstables during incremental repair
[ https://issues.apache.org/jira/browse/CASSANDRA-8267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229884#comment-14229884 ]
Marcus Eriksson commented on CASSANDRA-8267:
--------------------------------------------
Did part of 8110 (just the version negotiation), pretty simple but, we have to bump messaging version which affects quite a few things, for example, we can't migrate schemas between different messaging versions (this could be special cased and fixed for this issue of course)
https://github.com/krummas/cassandra/commits/marcuse/8110 - simply splits out the "header" part of StreamInitMessage into its own message and replies with a 'maxVersion' to that message when setting up the connection to agree on a version to use.
I think we should go with the new message solution above though, less risky for a minor release
> Only stream from unrepaired sstables during incremental repair
> --------------------------------------------------------------
>
> Key: CASSANDRA-8267
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8267
> Project: Cassandra
> Issue Type: Bug
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Fix For: 2.1.3
>
>
> Seems we stream from all sstables even if we do incremental repair, we should limit this to only stream from the unrepaired sstables if we do incremental repair
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)