[jira] [Updated] (ZOOKEEPER-1207) strange ReadOnlyZooKeeperServer ERROR when starting ensemble

["Patrick Hunt (Updated) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Hunt updated ZOOKEEPER-1207:
------------------------------------

    Priority: Critical  (was: Blocker)

Seems this is some weird error message that should not be output, but at the EOD is not a problem in itself. Would be great to get into 3.4.0 (avoid user confusion) but not a blocker.
                
> strange ReadOnlyZooKeeperServer ERROR when starting ensemble
> ------------------------------------------------------------
>
>                 Key: ZOOKEEPER-1207
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1207
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: quorum, server
>            Reporter: Patrick Hunt
>            Priority: Critical
>             Fix For: 3.4.0, 3.5.0
>
>
> I'm seeing a strange ERROR message when starting an ensemble:
> {noformat}
> 2011-09-27 13:00:08,168 [myid:3] - ERROR [Thread-2:QuorumPeer$1@689] - FAILED to start ReadOnlyZooKeeperServer
> java.lang.InterruptedException: sleep interrupted
> 	at java.lang.Thread.sleep(Native Method)
> 	at org.apache.zookeeper.server.quorum.QuorumPeer$1.run(QuorumPeer.java:684)
> {noformat}
> I did not specify ReadOnlyZooKeeperServer, also why is this at ERROR level? I'm not sure the expected behavior here. Is r/o turned on by default? Seems we should have this as a config option, off by default.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira