CentOS (linux) is same
On Sun, Sep 27, 2009 at 1:03 AM, Igor Katkov wrote:
> I applied the patch, logs segments are still not deleted
> but at least with this extra logging I found something - it says "Not safe
> to delete commit log
> c:/cassandra-4rc/data/commitlog\CommitLog-1254027292143.log;
I applied the patch, logs segments are still not deleted
but at least with this extra logging I found something - it says "Not safe
to delete commit log
c:/cassandra-4rc/data/commitlog\CommitLog-1254027292143.log; dirty is 1"
please see log snippet below, I grepped all lines that contain
"125402729
No, here I grepped all lines that contained word "flush"
http://www.katkovonline.com/flush.txt
On Sat, Sep 26, 2009 at 8:42 AM, Jonathan Ellis wrote:
> On Fri, Sep 25, 2009 at 11:55 PM, Igor Katkov wrote:
> > I checked out and built 0.4 branch. It's all the same, files stays.
>
> If you turn on
Ladies and gentlemen, I give you Cassandra 0.4.0.
It's hard to imagine that it has only been 2 months since our very first
release[1]; an impressive amount of progress has been made. For example:
* Nodes can now scale to billions of keys instead of millions.
* There is support for multiple keysp
Patch 0001 on https://issues.apache.org/jira/browse/CASSANDRA-459
fixes another bug that could cause this.
On Fri, Sep 25, 2009 at 11:55 PM, Igor Katkov wrote:
> I checked out and built 0.4 branch. It's all the same, files stays.
> I also noticed a side effect - as number of commit log segments i
No, it does not have to read commit log segments except on log replay.
On Fri, Sep 25, 2009 at 11:55 PM, Igor Katkov wrote:
> I checked out and built 0.4 branch. It's all the same, files stays.
> I also noticed a side effect - as number of commit log segments is
> growing, server response time is
On Fri, Sep 25, 2009 at 11:55 PM, Igor Katkov wrote:
> I checked out and built 0.4 branch. It's all the same, files stays.
If you turn on debug logging, does it show sstable flushing?
-Jonathan
