Bookkeeper server cannot re-connect to the zookeeper until zookeeper recognizes
-------------------------------------------------------------------------------
Key: BOOKKEEPER-116
URL: https://issues.apache.org/jira/browse/BOOKKEEPER-116
Project: Bookkeeper
Issue Type: Bug
Components: hedwig-client
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);
Reporter: Daniel Kim
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).
--
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
