[ https://issues.apache.org/jira/browse/HBASE-8359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635259#comment-13635259 ]
Hudson commented on HBASE-8359: ------------------------------- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #503 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/503/]) HBASE-8359 Too much logs on HConnectionManager (Revision 1469203) Result = FAILURE nkeywal : Files : * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java > Too much logs on HConnectionManager > ----------------------------------- > > Key: HBASE-8359 > URL: https://issues.apache.org/jira/browse/HBASE-8359 > Project: HBase > Issue Type: Bug > Components: Client > Affects Versions: 0.95.0 > Reporter: Nicolas Liochon > Assignee: Nicolas Liochon > Fix For: 0.98.0, 0.95.1 > > Attachments: 8359.v1.patch > > > Under a YCSB load test (for HBASE-6295), we can have sporadic bulk of logs > because of this: > {code} > final RegionMovedException rme = RegionMovedException.find(exception); > if (rme != null) { > LOG.info("Region " + regionInfo.getRegionNameAsString() + " moved to > " + > rme.getHostname() + ":" + rme.getPort() + " according to " + > source.getHostnamePort()); > updateCachedLocation( > regionInfo, source, rme.getServerName(), rme.getLocationSeqNum()); > } else if (RegionOpeningException.find(exception) != null) { > LOG.info("Region " + regionInfo.getRegionNameAsString() + " is being > opened on " > + source.getHostnamePort() + "; not deleting the cache entry"); > } else { > deleteCachedLocation(regionInfo, source); > } > {code} > They should just be removed. -- 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