You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Michi Mutsuzaki (JIRA)" <ji...@apache.org> on 2014/04/25 21:29:15 UTC

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

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

Michi Mutsuzaki resolved ZOOKEEPER-1207.
----------------------------------------

      Resolution: Invalid
    Release Note: Thanks Rakesh. I'm closing this as invalid since this has been fixed by  ZOOKEEPER-1268.

> 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.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 was sent by Atlassian JIRA
(v6.2#6252)