[
https://issues.apache.org/jira/browse/CASSANDRA-5220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658262#comment-14658262
]
Marcus Olsson edited comment on CASSANDRA-5220 at 8/5/15 2:15 PM:
------------------------------------------------------------------
While looking at CASSANDRA-5839 I realized that this might break something
during upgrade from 2.2->3.0, with this patch the table _repair_history_
changes to have a set of ranges instead of a start and end range.
Should I change the table back and do one insert per range instead?
was (Author: molsson):
While looking at CASSANDRA-5839 I realized that this might break something
during upgrade from 2.2->3.0, with this patch the table _repair_history_
changes to have a set of ranges instead of a start and end range. (This patch
was first done when
Should I change the table back and do one insert per range instead?
> Repair improvements when using vnodes
> -------------------------------------
>
> Key: CASSANDRA-5220
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5220
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.2.0 beta 1
> Reporter: Brandon Williams
> Assignee: Marcus Olsson
> Labels: performance, repair
> Attachments: 5220-yourkit.png, 5220-yourkit.tar.bz2,
> cassandra-3.0-5220-1.patch, cassandra-3.0-5220-2.patch,
> cassandra-3.0-5220.patch
>
>
> Currently when using vnodes, repair takes much longer to complete than
> without them. This appears at least in part because it's using a session per
> range and processing them sequentially. This generates a lot of log spam
> with vnodes, and while being gentler and lighter on hard disk deployments,
> ssd-based deployments would often prefer that repair be as fast as possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
