You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Geoffrey Jacoby (Jira)" <ji...@apache.org> on 2020/08/19 17:21:00 UTC
[jira] [Created] (HBASE-24909) Remove unnecessary
ClassNotFoundException and NoSuchMethodException stack traces from HBase
startup logs
Geoffrey Jacoby created HBASE-24909:
---------------------------------------
Summary: Remove unnecessary ClassNotFoundException and NoSuchMethodException stack traces from HBase startup logs
Key: HBASE-24909
URL: https://issues.apache.org/jira/browse/HBASE-24909
Project: HBase
Issue Type: Improvement
Reporter: Geoffrey Jacoby
Assignee: Geoffrey Jacoby
During cluster startup there are a couple of places where HBase needs to use reflection to determine what version of Hadoop or protobuf it's using, and then instantiate the right class.
If its first guess is wrong, it logs a ClassNotFoundException (for protobuf MessageLite) or NoSuchMethodException (for DFSClient.decryptEncryptedDataEncryptionKey). While this is done at DEBUG level, the exception types and the stack traces can lead to operators thinking something is wrong.
Since neither the exception nor the stack trace is actually of interest, we should just log a brief, clear message at DEBUG level about which decision was made and eat the exception without logging it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)