Yes.One thread is too old.In cassandra documents they just mentioned
commit logs can be clear after flush or drain.I have registered to the
mailing list.Currently I'm to going through it.If i found anything regard
of this matter I ll update.
On Sat, Jul 21, 2012 at 12:08 AM, Tharindu Mathew wro
Are you using the cassandra mailing list? They are quite helpful. The
threads you refer to are quite old, as they are incubator threads.
On Sat, Jul 21, 2012 at 12:01 AM, Harsha Kumara wrote:
> Hi!
>
> I was looked at that.Flushing is a safe way to delete the
> commitogs(Draining cause flushing
Hi!
I was looked at that.Flushing is a safe way to delete the
commitogs(Draining cause flushing all columnfamilies and stop accepting
write requests to cassandra node).They still not replied to my forum post
in cassandra forum.Below two threads discuss about this matter.But only say
flushing and d
Hi,
Have you looked at this? (Which i found in wiki)
Commit Log gets very big. Cassandra does not delete "old" commit logs. Why?
You probably have one or more Column Families with very low throughput.
These will typically not be flushed by crossing the throughput or
operations thresholds, causing
On Fri, Jul 20, 2012 at 2:46 PM, Tharindu Mathew wrote:
> Hi Harsha,
>
> Any luck with this?
>
They only defining a maximum size for log file.When logs filling up there
is maximum size for commit log.Default maximum size is normally 4GB.But
they not mention about automatic log file removing proce
Hi Harsha,
Any luck with this?
On Mon, Jul 16, 2012 at 6:49 AM, Harsha Kumara wrote:
>
>
> On Sun, Jul 15, 2012 at 12:27 PM, Deependra Ariyadewa wrote:
>
>>
>>
>> On Fri, Jul 13, 2012 at 11:39 PM, Tharindu Mathew wrote:
>>
>>> This has been there for some time now. Who's looking into this?
>>>
On Sun, Jul 15, 2012 at 12:27 PM, Deependra Ariyadewa wrote:
>
>
> On Fri, Jul 13, 2012 at 11:39 PM, Tharindu Mathew wrote:
>
>> This has been there for some time now. Who's looking into this?
>>
> Harsha Kumara did some research and found the flush and delete logs
> workaround. Harsh and Deep wo
On Sun, Jul 15, 2012 at 1:02 AM, Tharindu Mathew wrote:
> We need this before 20th (that's the beta release)...
ok, We will come with a solution.
Thanks,
Deependra.
>
>
> On Sun, Jul 15, 2012 at 12:27 PM, Deependra Ariyadewa wrote:
>
>>
>>
>> On Fri, Jul 13, 2012 at 11:39 PM, Tharindu Mathew
We need this before 20th (that's the beta release)...
On Sun, Jul 15, 2012 at 12:27 PM, Deependra Ariyadewa wrote:
>
>
> On Fri, Jul 13, 2012 at 11:39 PM, Tharindu Mathew wrote:
>
>> This has been there for some time now. Who's looking into this?
>>
> Harsha Kumara did some research and found th
On Fri, Jul 13, 2012 at 11:39 PM, Tharindu Mathew wrote:
> This has been there for some time now. Who's looking into this?
>
Harsha Kumara did some research and found the flush and delete logs
workaround. Harsh and Deep working on the issue.
Thank,
Deependra.
> Regards,
>
> Tharindu
> Sent fro
This has been there for some time now. Who's looking into this?
Regards,
Tharindu
Sent from my Android© device
On Jul 14, 2012 5:20 AM, "Deependra Ariyadewa" wrote:
>
>
> On Fri, Jul 13, 2012 at 1:03 PM, Sinthuja Ragendran wrote:
>
>> Hi,
>>
>> On Thu, Jun 21, 2012 at 10:15 PM, Deependra Ariya
On Fri, Jul 13, 2012 at 1:03 PM, Sinthuja Ragendran wrote:
> Hi,
>
> On Thu, Jun 21, 2012 at 10:15 PM, Deependra Ariyadewa wrote:
>
>>
>>
>> On Thu, Jun 21, 2012 at 10:07 PM, Afkham Azeez wrote:
>>
>>>
>>>
>>> On Thu, Jun 21, 2012 at 10:03 PM, Deependra Ariyadewa wrote:
>>>
On Thu,
Hi,
On Thu, Jun 21, 2012 at 10:15 PM, Deependra Ariyadewa wrote:
>
>
> On Thu, Jun 21, 2012 at 10:07 PM, Afkham Azeez wrote:
>
>>
>>
>> On Thu, Jun 21, 2012 at 10:03 PM, Deependra Ariyadewa wrote:
>>
>>>
>>>
>>> On Thu, Jun 21, 2012 at 9:12 PM, Afkham Azeez wrote:
>>>
Has this been sorted
On Thu, Jun 21, 2012 at 10:07 PM, Afkham Azeez wrote:
>
>
> On Thu, Jun 21, 2012 at 10:03 PM, Deependra Ariyadewa wrote:
>
>>
>>
>> On Thu, Jun 21, 2012 at 9:12 PM, Afkham Azeez wrote:
>>
>>> Has this been sorted out?
>>
>>
>> It looks we need operational solution for this.
>>
>> Cassandra creat
On Thu, Jun 21, 2012 at 10:03 PM, Deependra Ariyadewa wrote:
>
>
> On Thu, Jun 21, 2012 at 9:12 PM, Afkham Azeez wrote:
>
>> Has this been sorted out?
>
>
> It looks we need operational solution for this.
>
> Cassandra creates a 128MB commit log for every restart and it is safe to
> delete commi
On Thu, Jun 21, 2012 at 9:12 PM, Afkham Azeez wrote:
> Has this been sorted out?
It looks we need operational solution for this.
Cassandra creates a 128MB commit log for every restart and it is safe to
delete commit logs after flush all the data in node to hard disk.
Cassandra database folder
Has this been sorted out?
On Tue, Jun 19, 2012 at 12:34 PM, Deependra Ariyadewa wrote:
>
>
> On Tue, Jun 19, 2012 at 12:31 PM, Samisa Abeysinghe wrote:
>
>> Might want to check with Cassandra community
>>
>> On Tue, Jun 19, 2012 at 12:29 PM, Tharindu Mathew wrote:
>>
>>> I was running a BAM serv
On Tue, Jun 19, 2012 at 12:31 PM, Samisa Abeysinghe wrote:
> Might want to check with Cassandra community
>
> On Tue, Jun 19, 2012 at 12:29 PM, Tharindu Mathew wrote:
>
>> I was running a BAM server for some time (not continuously, restarting
>> all the time), and noticed the Cassandra data has g
Might want to check with Cassandra community
On Tue, Jun 19, 2012 at 12:29 PM, Tharindu Mathew wrote:
> I was running a BAM server for some time (not continuously, restarting all
> the time), and noticed the Cassandra data has grown to over 11 GB. I did
> not do any load test to get this kind of
I was running a BAM server for some time (not continuously, restarting all
the time), and noticed the Cassandra data has grown to over 11 GB. I did
not do any load test to get this kind of data growth. It seems the commit
logs are the culprit.
We need to figure out why this takes place. I have see
20 matches
Mail list logo
