Zhou wenjian created HBASE-7111:
-----------------------------------
Summary: hbase zkcli will not start if the zookeeper server
choosen to connectted to is not available
Key: HBASE-7111
URL: https://issues.apache.org/jira/browse/HBASE-7111
Project: HBase
Issue Type: Bug
Components: Zookeeper
Affects Versions: 0.94.2
Reporter: Zhou wenjian
Assignee: Zhou wenjian
Fix For: 0.94.4
there are 3 zookeeper servers in my cluster.
s1
s2
s3
after killing s3, i found the hbase zkcli will not start again.
it will try to connect to s3 continuely.
/11/07 11:01:01 INFO zookeeper.ClientCnxn: Opening socket connection to server
s3
12/11/07 11:01:01 WARN zookeeper.ClientCnxn: Session 0x0 for server null,
unexpected error, closing socket connection and attempting reconnect
java.net.ConnectException: Connection refused
from the code
public String parse(final Configuration c) {
// Note that we do not simply grab the property
// HConstants.ZOOKEEPER_QUORUM from the HBaseConfiguration because the
// user may be using a zoo.cfg file.
Properties zkProps = ZKConfig.makeZKProps(c);
String host = null;
String clientPort = null;
for (Entry<Object, Object> entry: zkProps.entrySet()) {
String key = entry.getKey().toString().trim();
String value = entry.getValue().toString().trim();
if (key.startsWith("server.") && host == null) {
String[] parts = value.split(":");
host = parts[0];
} else if (key.endsWith("clientPort")) {
clientPort = value;
}
if (host != null && clientPort != null) break;
}
return host != null && clientPort != null? host + ":" + clientPort: null;
}
the code will choose the fixed zookeeper server (here is the unavailable s3),
which leads to the script fails
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
