cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "B. Todd Burruss" <bburr...@real.com>
Subject Re: repair cause large number of SSTABLEs
Date Thu, 27 Jan 2011 19:27:13 GMT
[cassandra@kv-app02 ~]$ ls -l /data/cassandra-data/data/Queues/*Data.db 
| grep -c -v "\-tmp\-"
824

[cassandra@kv-app02 ~]$ ls -l 
/data/cassandra-data/data/Queues/*-tmp-*Data.db | wc -l
829

[cassandra@kv-app02 ~]$ ls -l /data/cassandra-data/data/Queues/*Comp* | 
wc -l
247


On 01/27/2011 11:14 AM, Stu Hood wrote:
>
> When the destination node fails to open the streamed SSTable, we 
> assume it was corrupted during transfer, and retry the stream. 
> Independent of the exception posted above, it is a problem that the 
> failed transfers were not cleaned up.
>
> How many of the data files are marked as -tmp-?
>
> On Jan 27, 2011 9:00 AM, "B. Todd Burruss" <bburruss@real.com 
> <mailto:bburruss@real.com>> wrote:
> > ok thx. what about the repair creating hundreds of new sstables and
> > lsof showing cassandra using currently over 800 Data.db files? is this
> > normal?
> >
> > On 01/27/2011 08:40 AM, Brandon Williams wrote:
> >> On Thu, Jan 27, 2011 at 10:21 AM, Todd Burruss <bburruss@real.com 
> <mailto:bburruss@real.com>
> >> <mailto:bburruss@real.com <mailto:bburruss@real.com>>> wrote:
> >>
> >> thx, but i didn't do anything like removing/adding nodes. just
> >> did a "nodetool repair" after running for an hour or so on a clean
> >> install
> >>
> >>
> >> It affects anything that involves streaming.
> >>
> >> -Brandon

Mime
View raw message