cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-11713) Add ability to log thread dump when NTR pool is blocked
Date Wed, 04 May 2016 22:44:12 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-11713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Paulo Motta updated CASSANDRA-11713:
------------------------------------
    Description: 
Thread dumps are very useful for troubleshooting Native-Transport-Requests contention issues
like CASSANDRA-11363 and CASSANDRA-11529.

While they could be generated externally with {{jstack}}, sometimes the conditions are transient
and it's hard to catch the exact moment when they happen, so it could be useful to generate
and log them upon user request when certain internal condition happens.

I propose adding a {{logThreadDumpOnNextContention}} flag to {{SEPExecutor}} that when enabled
via JMX generates and logs a single thread dump on the system log when the thread pool queue
is full.

  was:
Thread dumps are very useful for troubleshooting thread pool contention issues like CASSANDRA-11363
and CASSANDRA-11529.

While they could be generated externally with {{jstack}}, sometimes the conditions are transient
and it's hard to catch the exact moment when they happen, so it could be useful to generate
and log them upon user request when certain internal condition happens.

I propose adding a {{logThreadDumpOnNextContention}} flag to {{SEPExecutor}} and {{JMXEnabledThreadPoolExecutor}}
that when enabled via JMX generates and logs a single thread dump on the system log when the
thread pool queue is full.

        Summary: Add ability to log thread dump when NTR pool is blocked  (was: Add ability
to log thread dump when thread pool is full/blocked)

> Add ability to log thread dump when NTR pool is blocked
> -------------------------------------------------------
>
>                 Key: CASSANDRA-11713
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11713
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Observability
>            Reporter: Paulo Motta
>            Assignee: Paulo Motta
>            Priority: Minor
>
> Thread dumps are very useful for troubleshooting Native-Transport-Requests contention
issues like CASSANDRA-11363 and CASSANDRA-11529.
> While they could be generated externally with {{jstack}}, sometimes the conditions are
transient and it's hard to catch the exact moment when they happen, so it could be useful
to generate and log them upon user request when certain internal condition happens.
> I propose adding a {{logThreadDumpOnNextContention}} flag to {{SEPExecutor}} that when
enabled via JMX generates and logs a single thread dump on the system log when the thread
pool queue is full.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message