James Taylor created HBASE-12039:
------------------------------------
Summary: Lower log level for TableNotFoundException log message
when throwing
Key: HBASE-12039
URL: https://issues.apache.org/jira/browse/HBASE-12039
Project: HBase
Issue Type: Bug
Reporter: James Taylor
Our HBase client tries to get the HTable descriptor for a table that may or may
not exist. We catch and ignore the TableNotFoundException if it occurs, but the
log message appear regardless of this which confuses our users. Would it be
possible to lower the log level of this message since the exception is already
being throw (making it up to the caller how they want to handle this).
14/09/20 20:01:54 WARN client.HConnectionManager$HConnectionImplementation:
Encountered problems when prefetch META table:
org.apache.hadoop.hbase.TableNotFoundException: Cannot find row in .META. for
table: _IDX_TEST.TESTING, row=_IDX_TEST.TESTING,,99999999999999
at
org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:151)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.prefetchRegionCache(HConnectionManager.java:1059)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:1121)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:1001)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:958)
at org.apache.hadoop.hbase.client.HTable.finishSetup(HTable.java:251)
at org.apache.hadoop.hbase.client.HTable.<init>(HTable.java:243)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
