Log maxClientCnxn warning in INFO level
---------------------------------------
Key: ZOOKEEPER-1325
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1325
Project: ZooKeeper
Issue Type: Improvement
Components: server
Affects Versions: 3.4.0, 3.3.4, 3.3.3
Reporter: Mubarak Seyed
Priority: Minor
When Hbase client ZooKeeperWatcher gets ConnectionLossException (/hbase/rs or
/hbase), it is very hard debug the ZK server log if ZK server has started using
log4j INFO level.
When maxClientCnxn limit is reached for a single client (at the socket level),
it will be nice to log it in INFO level instead of WARN. It will help hbase
clients (Region server, HMaster, and HBase cient lib) to debug the issue in
production.
{code}
3.4 - src/java/main/org/apache/zookeeper/server/NIOServerCnxnFactory.java
3.3.4 - src/java/main/org/apache/zookeeper/server/NIOServerCnxn.java
public void run() {
while (!ss.socket().isClosed()) {
try {
...
...
if (maxClientCnxns > 0 && cnxncount >= maxClientCnxns){
LOG.info("Too many connections from " + ia
+ " - max is " + maxClientCnxns );
sc.close();
}
...
}
{code}
--
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
