Thanks Jonathan. I guess i need to be patient for JVM GC :-) Two more things i was trying, and wanted to check if it was supported. Now, i have a 2 node cluster (say A and B), and i am trying to bootstrap 2 more nodes. (C and D) The first bootstrap started successfully. I see anticompaction happenning on C for the purpose, and hopefully streaming shall start soon from C -> A The second bootstrap I started only after the first one said bootstrapping (as mentioned on the wiki). However, it just sits there, doing nothing (or so I think! :-)). D machine says its bootstrapping from B, and is supposed to assume load from B. B just sits there, doing nothing.. unlike the first case where I could see A machine logging messages about anticompaction.
D was once a part of the cluster, but had gone down because of disk issues. Its back up, it still has the old data, however to bootstrap again, i deleted the old Location db (is that a good practise?), and so i see it did take a new token, but is not proceeding with the bootstrap. I wanted to see, if bootstrap goes correctly in such cases, and testing nodetool cleanup after that, and the amount of time all these things take. Also, a question about the storage config file. When I brought up B, the seeds configured in B's config was just A. When I am bringing up C and D, the seeds configured in their config file are both A and B. B's config still says the seed is A. For B to be a seed, does its own config need to also say that its a seed. Thanks for all the help, Gurpreet On Thu, Sep 9, 2010 at 7:25 AM, Jonathan Ellis <jbel...@gmail.com> wrote: > On Thu, Sep 9, 2010 at 12:50 AM, Gurpreet Singh > <gurpreet.si...@gmail.com> wrote: > > 1. what is the purpose of this anticompacted file created during cleanup? > > That is all the data that still belongs to the node, post-bootstrap. > Since you were just bringing the cluster back up to RF nodes, that's > all the data it started with still. The older files will be removed > after the next JVM GC (or server restart, whichever comes first): > http://wiki.apache.org/cassandra/MemtableSSTable > > > 2. compaction is also supposed to create a big file after reconciling the > > sstable files.. i see that anti-compaction is also creating a big file. > How > > are these files going to be different? > > Anticompaction is for splitting out one range of data from the rest. > > > 3. Other than during streaming (bootstrapping), when is anti-compaction > > triggered? > > It's not. > > > 4. Now i have 240 gigs of disk used for probably around 92 gigs of useful > > data. When will the other files get deleted? Do i need to run compaction > > separately to take care of this. > > Answered above. > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of Riptano, the source for professional Cassandra support > http://riptano.com >
