You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Rakesh R (Commented) (JIRA)" <ji...@apache.org> on 2011/09/30 08:56:45 UTC
[jira] [Commented] (ZOOKEEPER-1207) strange ReadOnlyZooKeeperServer
ERROR when starting ensemble
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117921#comment-13117921 ]
Rakesh R commented on ZOOKEEPER-1207:
-------------------------------------
Hi Pat,
Yes, Presently there is no config option for enabling or disabling r/o and turned on by default. I also feel it can be turned off by default and can give config options (IMO we can follow the similar pattern of 'Observer' ZooKeeper server startup.)
For ex: In zoo.cfg,
server.1=10.18.52.25:2252:2252:readonly
or
peerType=readonly
If you agree I can work on the approach. Suggest me if any better solution.
*Cause of exception:-*
After spawing the rozk, quorumpeer is going ahead with lookForLeader().
Since this has completed within 'sleep(Math.max(2000, tickTime));' and interrupting rozk thread inorder to avoid the startup of rozk('fastfail' approach).
Thanks,
Rakesh
> 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