Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1425CE2D5 for ; Fri, 7 Dec 2012 23:59:23 +0000 (UTC) Received: (qmail 39357 invoked by uid 500); 7 Dec 2012 23:59:21 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 39247 invoked by uid 500); 7 Dec 2012 23:59:21 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 38974 invoked by uid 99); 7 Dec 2012 23:59:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Dec 2012 23:59:21 +0000 Date: Fri, 7 Dec 2012 23:59:21 +0000 (UTC) From: "Carl Yeksigian (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CASSANDRA-5044) Allow resizing of threadpools via JMX MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Carl Yeksigian created CASSANDRA-5044: ----------------------------------------- Summary: Allow resizing of threadpools via JMX Key: CASSANDRA-5044 URL: https://issues.apache.org/jira/browse/CASSANDRA-5044 Project: Cassandra Issue Type: Improvement Reporter: Carl Yeksigian Assignee: Carl Yeksigian Priority: Minor Attachments: 5044.txt Currently changing the size of threadpools is done using the config files. If resizing a threadpool, the node needs to be taken offline. Adding resizing via JMX allows online tweaking. TPEs allow for moving the number of threads up and down; moving down will take effect after a thread in the pool becomes idle. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira