Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zookeeper.apache.org
Date: Mon, 1 Aug 2011 17:32:09 +0000 (UTC)
From: "Patrick Hunt (JIRA)" <jira@apache.org>
To: dev@zookeeper.apache.org
Message-ID: 
 <969772587.23231.1312219929728.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1301903844.19228.1311958209845.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (ZOOKEEPER-1140) server shutdown is not stopping
 threads
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ZOOKEEPER-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073620#comment-13073620 ] 

Patrick Hunt commented on ZOOKEEPER-1140:
-----------------------------------------

bq. Pat, I think you had some insight for why it should be off by default. Could you remind me what it is, please?

We don't want to change the default behavior of the server during a minor release - if people upgrade they may not be expecting the server to drop into r/o mode automatically. New features such as this should be "off by default" with a configuration option to enable.


> server shutdown is not stopping threads
> ---------------------------------------
>
>                 Key: ZOOKEEPER-1140
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1140
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: server, tests
>    Affects Versions: 3.4.0
>            Reporter: Patrick Hunt
>            Priority: Blocker
>             Fix For: 3.4.0
>
>
> Near the end of QuorumZxidSyncTest there are tons of threads running - 115 "ProcessThread" threads, similar numbers of SessionTracker.
> Also I see ~100 ReadOnlyRequestProcessor - why is this running as a separate thread? (henry/flavio?)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira