Hi Philippe,
On Thu, Sep 29, 2011 at 6:47 AM, Philippe wrote:
> No it was an upgrade from 0.8.4 or 0.8.5 depending on the nodes.
> No cassandra-env files were changed during the update.
> Any other ideas? The cluster has just been weird ever since running 0.8.6 :
> has anyone else upgraded and n
No it was an upgrade from 0.8.4 or 0.8.5 depending on the nodes.
No cassandra-env files were changed during the update.
Any other ideas? The cluster has just been weird ever since running 0.8.6 :
has anyone else upgraded and not run into this?
Le 28 sept. 2011 09:32, "Peter Schuller" a
écrit :
>>
> I have changed absolutely nothing and the work load is perhaps even lower
> than before upgrading because I have paused most updates to the cluster. Did
> a log level change or does this have deeper meaning ?
You don't say which version you upgraded from but I suspect 0.7? JVM
options like heap
Ever since upgrading to 0.8.6, my nodes' system.log is littered with
GCInspector logs such as these
INFO [ScheduledTasks:1] 2011-09-26 21:23:40,468 GCInspector.java (line 122)
GC for ParNew: 209 ms for 1 collections, 4747932608 used; max is 16838033408
INFO [ScheduledTasks:1] 2011-09-26 21:23:43,7
