cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] Created: (CASSANDRA-1275) Log threadpool stats after excessive GC
Date Tue, 13 Jul 2010 17:57:50 GMT
Log threadpool stats after excessive GC
---------------------------------------

                 Key: CASSANDRA-1275
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1275
             Project: Cassandra
          Issue Type: Improvement
          Components: Core
            Reporter: Brandon Williams
            Assignee: Brandon Williams
            Priority: Trivial
             Fix For: 0.6.4
         Attachments: 1275.txt

When GC begins taking longer and longer, it is often a sign that the JVM is going OOM, but
it is not clear why.  Often, users swamp the MDP by either writing at CL.ZERO or issuing many
read requests while the machine is block on disk IO.  To more easily diagnose this, we should
log the threadpool stats when we see a GC take too long.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message