iving.properties, so I guess
>> I was not using commit log archiving.
>>
>> What I did was doing a lot of insertions (and some deletions)
>> using another 4 machines with 32 processes in total.
>> (There are 4 nodes in my setting, so there are 8 machines in total)
>&
unt of
> insertions.
> Right now I can't distinguish whether single insertion also cause huge
> logs.
>
> nodetool flush hanged (maybe because of 200G+ commitlog)
>
> Because these machines are not in production (guaranteed no more
> insertion/deletion)
> I en
amount of
>>>> insertions.
>>>> Right now I can't distinguish whether single insertion also cause huge
>>>> logs.
>>>>
>>>> nodetool flush hanged (maybe because of 200G+ commitlog)
>>>>
>>>> Because these ma
up restarting cassandra one node each time, the commitlog
>>> shrinked back to
>>> 4G. I am doing repair on each node now.
>>>
>>> I'll try to re-import and keep logs when the commitlog increases insanely
>>> again.
>>>
>>> Sincer
; insertion/deletion)
>> I ended up restarting cassandra one node each time, the commitlog
>> shrinked back to
>> 4G. I am doing repair on each node now.
>>
>> I'll try to re-import and keep logs when the commitlog increases insanely
>> again.
>>
>>
logs when the commitlog increases insanely
> again.
>
> Sincerely,
> Hsiao
>
>
> On Mon, Nov 19, 2012 at 3:19 AM, aaron morton
> wrote:
> > I am wondering whether the huge commitlog size is the expected behavior
> or
> > not?
> >
> > Nope.
commitlog increases insanely again.
Sincerely,
Hsiao
On Mon, Nov 19, 2012 at 3:19 AM, aaron morton wrote:
> I am wondering whether the huge commitlog size is the expected behavior or
> not?
>
> Nope.
>
> Did you notice the large log size during or after the inserts ?
> If after
> I am wondering whether the huge commitlog size is the expected behavior or
> not?
Nope.
Did you notice the large log size during or after the inserts ?
If after did the size settle ?
Are you using commit log archiving ? (in commitlog_archiving.properties)
> and around 700 mini colu
hi Cassandra Developers,
I am experiencing huge commitlog size (200+G) after inserting huge
amount of data.
It is a 4-node cluster with RF= 3, and currently each has 200+G commit
log (so there are around 1T commit log in total)
The setting of commitlog_total_space_in_mb is default.
I am using
