> INFO [ScheduledTasks:1] 2013-04-15 14:00:02,749 GCInspector.java (line
122) GC for ParNew: 338798 ms for 1 collections, 592212416 used; max is
1046937600
This says GC for New Generation took so long. And this is usually unlikely.
The only situation I am aware of is when a fairly large object is
Can you paste you gc config? Also can you take a heap dump at 2 diff points so
that we can compare it?
Quick thing to do would be to do a histo live at 2 points and compare
Sent from my iPhone
On Jun 15, 2013, at 6:57 AM, Takenori Sato wrote:
> > INFO [ScheduledTasks:1] 2013-04-15 14:00:02,74
Uncomment the followings in "cassandra-env.sh".
JVM_OPTS="$JVM_OPTS -XX:+PrintGCDateStamps"
JVM_OPTS="$JVM_OPTS -XX:+PrintPromotionFailure"
JVM_OPTS="$JVM_OPTS -Xloggc:/var/log/cassandra/gc-`date +%s`.log"
*> *Also can you take a heap dump at 2 diff points so that we can compare it?
No, I'm afr
> Also can you take a heap dump at 2 diff points so that we can compare it?
Also note that a promotion failure won't happen by a particular object, but
by a fragmentation in Old Generation space. So I am not sure if you can't
tell by a heap dump comparison.
On Sun, Jun 16, 2013 at 4:44 AM, Mohit
