Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 4 May 2016 22:44:12 +0000 (UTC)
From: "Paulo Motta (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12965107.1462399195000.113720.1462401852950@Atlassian.JIRA>
In-Reply-To: <JIRA.12965107.1462399195000@Atlassian.JIRA>
References: <JIRA.12965107.1462399195000@Atlassian.JIRA> <JIRA.12965107.1462399195335@arcas>
Subject: [jira] [Updated] (CASSANDRA-11713) Add ability to log thread dump
 when NTR pool is blocked
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 04 May 2016 22:44:15 -0000


     [ 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)