Uploaded image for project: 'Bookkeeper'
  1. Bookkeeper
  2. BOOKKEEPER-116

Bookkeeper server cannot re-connect to the zookeeper until zookeeper recognizes

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: hedwig-client
    • Labels:
      None
    • Environment:

      CentOS 5.5 for all servers and workstations (however zookeeper, bookies, and hubs are all built in Ubuntu 11);
      OpenJDK Runtime Environment (IcedTea6 1.9.10) (rhel-1.23.1.9.10.el5_7-i386);
      OpenJDK Client VM (build 19.0-b09, mixed mode);

      Description

      When a bookie is disconnected from the zk server, zk does not know about this immediately. As a result, if I try to restart the bookie, meanwhile, it will not be able to. Zk server believes that the server trying to reconnect already has a connection. Instead of throwing KeeperException for existing node, zk server should wait until the pre-existing connection times out and tries to reconnect. Or zk server should ignore the old metadata about this node, and re-connect immediately (but I guess this solution may cause security issues).

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                ksw2599 Daniel Kim
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 72h
                  72h
                  Remaining:
                  Remaining Estimate - 72h
                  72h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified