[
https://issues.apache.org/jira/browse/ZOOKEEPER-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073264#comment-13073264
]
Flavio Junqueira commented on ZOOKEEPER-1140:
---------------------------------------------
Some comments:
# Waiting for some grace period to start the RO zookeeper server avoids
switching back and forth frequently when connectivity is intermittent;
# Calling startup() in a new thread makes sense because otherwise we hold
leader election until the grace period for RO expires. The alternative I see is
to check for this grace period in the beginning of the run() method of
RORequestProcessor;
# shutdown() should have no effect if the zookeeper server hasn't started. Are
you concerned that we might end up creating RO zookeeper servers and using them
unnecessarily?
# Pat, I think you had some insight for why it should be off by default. Could
you remind me what it is, please?
> 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
