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 5684A10402 for ; Fri, 3 Jan 2014 13:36:56 +0000 (UTC) Received: (qmail 60910 invoked by uid 500); 3 Jan 2014 13:36:52 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 60876 invoked by uid 500); 3 Jan 2014 13:36:51 -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 60849 invoked by uid 99); 3 Jan 2014 13:36:50 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Jan 2014 13:36:50 +0000 Date: Fri, 3 Jan 2014 13:36:50 +0000 (UTC) From: "Jason Harvey (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-6546) disablethrift followed by enablethrift results in unclosed file descriptors MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-6546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Harvey updated CASSANDRA-6546: ------------------------------------ Description: -Disabling and then re-enabling thrift resulted in this stat reporting double the number of connected sockets on the service. Alternatively, if the metric is accurate, then disabling and then re-enabling thrift may be resulting in a bunch of unused FDs? Reproducing is easy. Have a handful of thrift clients, disablethrift, wait a few minutes, re-enable thrift, have your client apps reconnect, then compare actual connected sockets (via netstat or lsof or what have you) to the value from this MBean ( org.apache.cassandra.metrics:type=Client,name=connectedThriftClients ).- was: Disabling and then re-enabling thrift resulted in this stat reporting double the number of connected sockets on the service. Alternatively, if the metric is accurate, then disabling and then re-enabling thrift may be resulting in a bunch of unused FDs? Reproducing is easy. Have a handful of thrift clients, disablethrift, wait a few minutes, re-enable thrift, have your client apps reconnect, then compare actual connected sockets (via netstat or lsof or what have you) to the value from this MBean ( org.apache.cassandra.metrics:type=Client,name=connectedThriftClients ). > disablethrift followed by enablethrift results in unclosed file descriptors > --------------------------------------------------------------------------- > > Key: CASSANDRA-6546 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6546 > Project: Cassandra > Issue Type: Bug > Reporter: Jason Harvey > Priority: Minor > > -Disabling and then re-enabling thrift resulted in this stat reporting double the number of connected sockets on the service. > Alternatively, if the metric is accurate, then disabling and then re-enabling thrift may be resulting in a bunch of unused FDs? > Reproducing is easy. Have a handful of thrift clients, disablethrift, wait a few minutes, re-enable thrift, have your client apps reconnect, then compare actual connected sockets (via netstat or lsof or what have you) to the value from this MBean ( org.apache.cassandra.metrics:type=Client,name=connectedThriftClients ).- -- This message was sent by Atlassian JIRA (v6.1.5#6160)