OR1dk
>
> This hammered reads from our application tier (writes seemed okay) and
> until we determine what the root cause is, we'd like to be able to start
> Cassandra with gossip disabled.
>
> Is this possible?
> Thanks
> .bN
>
--
Dominic Letz // Director of
I delete all data
> for that node and run repair. Does node repair check the ttl value before
> retrieving data from other nodes? Do you have any other suggestions?
>
> Best Regards,
> Cem.
>
--
Dominic Letz
Director of R&D
Exosite <http://exosite.com>
ocess(row)
>
> }
>
>
>
> Even after we reduced the page size to 1000, the C* nodes still crash. C*
> is running on M3.xlarge machines (4-cores, 15GB). We manually increased the
> heap size to 8GB just to see how much heap C* consumes. With 10-15 minutes,
> the heap usage climbs up to 7.6GB. That does not make sense. Either
> automatic paging is not working or we are missing something.
>
>
>
> Does anybody have insights as to what could be happening? Thanks.
>
>
>
> Mohammed
>
>
>
>
>
>
>
>
>
>
>
> --
>
> Thanks,
>
> Ryan Svihla
>
--
Dominic Letz
Director of R&D
Exosite <http://exosite.com>
2.1.2 with
>> default
>> configuration.
>>
>> What I observed, is that with 6-nodes and 9-nodes, the Cassandra servers
>> were doing OK with IO, but CPU utilization was about 60%~70% higher than
>> 3-nodes.
>>
>> I'd like to get suggestion how to troubleshoot this, as this is totally
>> against
>> what I read, that Cassandra is scaled linearly.
>>
>>
>>
>>
>
--
Dominic Letz
Director of R&D
Exosite <http://exosite.com>
