Matthew Dennis riptano.com> writes:
> Yes, please file it to Jira. It seems like it would be pretty useful for
various things and fairly easy to change the code to move it to another
directory whenever C* thinks it should be deleted...
Here it is for 0.6.4 version. Should work on a 0.6.5 as well
>
> PS. Are other ppl interested in this functionality ?
> I could file it to JIRA as well...
>
>
Yes, please file it to Jira. It seems like it would be pretty useful for
various things and fairly easy to change the code to move it to another
directory whenever C* thinks it should be deleted...
Thanks Oleg!
Could you please share the patch. I have build Cassandra before from source.
I can definitely give it try.
-Naren
On Wed, Oct 6, 2010 at 3:55 AM, Oleg Anastasyev wrote:
> > Is it possible to retain the commit logs?
>
> In off-the-shelf cassandra 0.6.5 this is not possible, AFAIK.
> PS. Are other ppl interested in this functionality ?
> I could file it to JIRA as well...
I was about to post that such a thing was useful for point-in-time
recovery before reading your post, so yes :)
--
/ Peter Schuller
> Is it possible to retain the commit logs?
In off-the-shelf cassandra 0.6.5 this is not possible, AFAIK.
I developed a patch we use internally in our company for commit
log archivation and replay.
I can share a patch with you, if you dare patching cassandra
sources by yourself ;-)
PS. Are o
If you turn the log level up to DEBUG that will include information about each
request. Would that help? You could restrict it by setting a logging
configuration for the specific classes that output the message you are
interested in.
Not sure about retaining the commit logs.
Aaron
On 6 Oct 20
Cassandra Version: 0.6.5
I am running a long duration test and I need to keep the commit log to see
the sequence of operations to debug few application issues. Is it possible
to retain the commit logs? Apart from increasing the value of
CommitLogRotationThresholdInMB
what is the other way to achie
