After some bad experiences in the past using non-release versions, I am a little hesitant. Which nodes would the new code have to be deployed to in order to test? If it is just one of the three, I might be willing if I need to repair again.
Dan From: Brandon Williams [mailto:dri...@gmail.com] Sent: January-24-11 19:19 To: user@cassandra.apache.org Subject: Re: Repair on single CF not working (0.7) On Mon, Jan 24, 2011 at 4:15 PM, Dan Hendry <dan.hendry.j...@gmail.com> wrote: I am trying to repair a single CF using nodetool. It seems like the request to limit the repair to one CF is not being respected. Here is my current situation: - Run "nodetool repair KEYSPACE CF_A" on node 3 - Validation compaction runs on nodes 2,3,4 for CF_A only (expected) - Node 3 streams SSTables from CF_A only to nodes 2 and 4 (expected) - Nodes 2 and 4 stream SSTables from ALL column families in the keyspace to node 2 (VERY unexpected) - Node 2 runs out of disk space before SSTable rebuild for all cfs can complete. Presumably this is a bug (?). This is the first time in quite awhile that I have run a repair (I don't perform deletes, just use expiring columns). I have included pertinent log entries below: Log entry from node 3 after running out of disk space: INFO [Thread-3462] 2011-01-24 16:00:40,658 StreamInSession.java (line 124) Streaming of file /var/lib/cassandra/data/kikmetrics/UserEventsByEvent-e-1313-Data.db/(0,28295 156514) progress=15267921920/28295156514 - 53% from org.apache.cassandra.streaming.StreamInSession@8df7e0c failed: requesting a retry. INFO [Thread-3423] 2011-01-24 16:00:40,658 StreamInSession.java (line 124) Streaming of file /var/lib/cassandra/data/kikmetrics/UserEventsByEvent-e-1348-Data.db/(2953062 0905,58066315307) progress=18898300928/28535694402 - 66% from org.apache.cassandra.streaming.StreamInSession@8df7e0c failed: requesting a retry. Can you test this against the 0.7 branch? There were some bugs fixed in StreamInSession that may be related (https://issues.apache.org/jira/browse/CASSANDRA-1992) -Brandon No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.872 / Virus Database: 271.1.1/3398 - Release Date: 01/24/11 02:35:00
