ZooKeeper
  1. ZooKeeper
  2. ZOOKEEPER-1207

strange ReadOnlyZooKeeperServer ERROR when starting ensemble

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 3.5.0
    • Component/s: quorum, server
    • Labels:
      None

      Description

      I'm seeing a strange ERROR message when starting an ensemble:

      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)
      

      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.

        Activity

        Hide
        Patrick Hunt added a comment -

        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.

        Show
        Patrick Hunt added a comment - 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.
        Hide
        Rakesh R added a comment -

        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

        Show
        Rakesh R added a comment - 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
        Hide
        Mahadev konar added a comment -

        Moving this to 3.4.1. We can skip Readonly ZK server for this release. There are multiple issues with it.

        Show
        Mahadev konar added a comment - Moving this to 3.4.1. We can skip Readonly ZK server for this release. There are multiple issues with it.

          People

          • Assignee:
            Unassigned
            Reporter:
            Patrick Hunt
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development