On Dec 27, 2010, at 14:34, Timo Nentwig wrote:
> On Dec 24, 2010, at 14:33, Timo Nentwig wrote:
>> Any advice what to do with it?
>
> So, to continue this monologue: I reduced the memtable size for that CF and
> the by means of the MBeans figured out that the secondary index is a CF as
> well
On Dec 24, 2010, at 14:33, Timo Nentwig wrote:
> Any advice what to do with it?
So, to continue this monologue: I reduced the memtable size for that CF and the
by means of the MBeans figured out that the secondary index is a CF as well
which presumably also holds up to 3 memtables in memory...
On Dec 23, 2010, at 12:34, Timo Nentwig wrote:
> On Dec 23, 2010, at 9:34, Timo Nentwig wrote:
>
>> I was about to add a secondary index (which apparently failed) to existing
>> data. When I restarted the node it crashed (!) with:
>
> It crashed because it ran out of heap space (2G). So I incr
On Dec 23, 2010, at 9:34, Timo Nentwig wrote:
> I was about to add a secondary index (which apparently failed) to existing
> data. When I restarted the node it crashed (!) with:
It crashed because it ran out of heap space (2G). So I increased to 3.5G but
after a whlie it's caught in full GC ag