SSTable files not getting deleted

My impression is that force GC should have deleted the SSTable files no longer valid. I performed a nodetool compact, all went good and finished. All column family now only have one big live SSTable file. Then I use jconsole to force a GC, but those old SSTable files still not getting deleted.

Re: SSTable files not getting deleted

> On Thu, Jan 6, 2011 at 7:59 AM, Ching-Cheng Chen > wrote: > > > I performed a nodetool compact, all went good and finished. All column > > family now only have one big live SSTable file. > > Then I use jconsole to force a GC, but those old SSTable files still not &g

Re: UnserializableColumnFamilyException: Couldn't find cfId

We have similar exception before, and the root cause was like Aaron mentioned. You will encounter this exception If you have code create CF on the fly and data was insert into the node which hasn't got schema synced yet. You will have to call describe_schema_version() to ensure all nodes has same

Files not deleted after compaction and GCed

Using cassandra 0.7.0 The class org.apache.cassandra.io.sstable.SSTableDeletingReference only remove the -Data.db file, but leave the xxx-Compacted, xxx-Filter.db, xxx-Index.db and xxx-Statistics.db intact. And that's the behavior I saw.I ran manual compact then trigger a GC from jconsole

Re: Files not deleted after compaction and GCed

Chen On Tue, Jan 25, 2011 at 4:05 PM, Jonathan Ellis wrote: > No, that is not expected. All the sstable components are removed in > the same method; did you check the log for exceptions? > > On Tue, Jan 25, 2011 at 2:58 PM, Ching-Cheng Chen > wrote: > > Usin

Re: Files not deleted after compaction and GCed

un(Unknown Source) Regards, Chen On Tue, Jan 25, 2011 at 4:21 PM, Jonathan Ellis wrote: > the other component types are deleted by this line: > >SSTable.delete(desc, components); > > On Tue, Jan 25, 2011 at 3:11 PM, Ching-Cheng Chen > wrote: > > Nope, no exc

Re: Files not deleted after compaction and GCed

> On Wed, Jan 26, 2011 at 9:41 AM, Jonathan Ellis wrote: > > Thanks for tracking that down! Created > > https://issues.apache.org/jira/browse/CASSANDRA-2059 to fix. > > > > On Wed, Jan 26, 2011 at 8:17 AM, Ching-Cheng Chen > > wrote: > >

memtable_flush_after_mins setting not working

We have observed the behavior that memtable_flush_after_mins setting not working occasionally. After some testing and code digging, we finally figured out what going on. The memtable_flush_after_mins won't work on certain condition with current implementation in Cassandra. In org.apache.cassandr

Re: memtable_flush_after_mins setting not working

eb 17, 2011 at 10:17 AM, Ching-Cheng Chen > wrote: > > We have observed the behavior that memtable_flush_after_mins setting not > > working occasionally. After some testing and code digging, we finally > > figured out what going on. > > The memtable_flush_after_mins wo

Re: memtable_flush_after_mins setting not working

https://issues.apache.org/jira/browse/CASSANDRA-2183 <https://issues.apache.org/jira/browse/CASSANDRA-2183>Regards, Chen www.evidentsoftware.com On Thu, Feb 17, 2011 at 11:47 AM, Ching-Cheng Chen < cc...@evidentsoftware.com> wrote: > Certainly, I'll open a ticket

Re: [RELEASE] 0.7.2

Looks like it's https://issues.apache.org/jira/browse/CASSANDRA-2172 Regards, Chen www.evidentsoftware.com On Thu, Feb 17, 2011 at 1:06 PM, Damick, Jeffrey wrote: > So after upgrade to 0.7.2, I see this on startup – should I just blow >

Re: Error when bringing up 3rd node

41 82 123 These certainly not correct. Can't just use 2 ^ 127, will overflow You can't use Java's primitive type to do this calculation. long only use 64 bit. You'd need to use BigInteger class to do this calculation. Regards, Chen www.evidentsoftware.com On Fri, Feb 18, 2011 at 4:04 PM,

Re: Error when bringing up 3rd node

try this BigInteger bi = new BigInteger("2"); BigInteger or = new BigInteger("2"); for (int i=1;i<127;i++) { or = or.multiply(bi); } or = or.divide(new BigInteger("3")); for (int i=0;i<3;i++) { System.out.println(or.multiply(new BigInteger(""+i))); } which generate 0 56713727820156410577229101

Re: Error when bringing up 3rd node

If you know you will have 3 nodes, you should set the initial token inside the cassandra.yaml for each node. Then you won't need to run nodetool move. Regards, Chen www.evidentsoftware.com On Fri, Feb 18, 2011 at 5:24 PM, mcasandra wrote: > > Thanks! I feel so horrible after realizing what m

Re: Is it possible to get list of row keys?

You can use the setRowCount() method to specify how many keys to return per call. By default is 100. Beware don't set it too high since it might cause OOM. And underline code will pre-allocate an array list with size you speify in setRowCount(). So you might get a OOM if you used something like

Re: Is it possible to get list of row keys?

urer wrote: > query per ranges is only possible with OPP or BPP. > > Bye, > Norman > > > 2011/2/23 Sasha Dolgy : > > What if i want 20 rows and the next 20 rows in a subsequent query? can > this > > only be achieved with OPP? > > > > -- > > Sasha Dolgy > > sasha.do...@gmail.com > > > > On 23 Feb 2011 13:54, "Ching-Cheng Chen" > wrote: > > >

Re: Is it possible to get list of row keys?

; > On 23/02/2011 15:24, Daniel Lundin wrote: > >> They are, however, in *stable* order, which is important. >> >> On Wed, Feb 23, 2011 at 3:20 PM, Norman Maurer wrote: >> >>> yes but be aware that the keys will not in the "right order". >>>

Re: Cassandra 0.7.2 - Enable/Disable HH via JMX (Jconsole)

The HintedHandoffEnabled attribute is read/write. You can always set it to true/false to enable/disable HH. Regards, Chen www.evidentosftware.com On Thu, Mar 3, 2011 at 1:47 PM, Narendra Sharma wrote: > I am unable to enable/disable HH via JMX (JConsole). > > Even though the load is on and re

Re: Cassandra 0.6.3 ring not balance in terms of data size

>From OrderPreservingPartition.java public StringToken getToken(ByteBuffer key) { String skey; try { skey = ByteBufferUtil.string(key, Charsets.UTF_8); } catch (CharacterCodingException e) { throw new RuntimeException(

Re: Meaning of TotalReadLatencyMicros and TotalWriteLatencyMicrosStatistics

Just as what it named, it's the total microseconds spent on read operations so far. Not average. Regards, Chen Senior Developer, EvidentSoftware(Leaders in Monitoring of NoSQL & JAVA ) http://www.evidentsoftware.com On Tue, Mar 22, 2011 at 11:11 AM, Jonathan Colby wrote: > Hi - > > On our re

Re: Problem about freeing space after a major compaction

tombstones removal also depends on your gc grace period setting. If you are pretty sure that you have proper gc grace period set and still on 0.7.0, then probably related to this bug. https://issues.apache.org/jira/browse/CASSANDRA-2059 Regards,

Re: Problem about freeing space after a major compaction

2011 at 11:04 AM, Roberto Bentivoglio < roberto.bentivog...@gmail.com> wrote: > Hi Chen, > we've set the gc grace period of the column families to 0 as suggest in a > single node enviroment. > Can this setting cause the problem? I don't think so... > > Thanks, &

Secondary index query return row should not return?

Not sure if this the intended behavior of the indexed query. I created a column family and added index on column A,B,C. Now I insert three rows. row1 : A=123, B=456, C=789 row2 : A=123, C=789 row3 : A=123, B=789, C=789 Now if I perform an indexed query for A=123 and B=456, both row1 and row2 ar