You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2020/04/30 21:52:00 UTC

[jira] [Created] (HBASE-24295) [Chaos Monkey] abstract logging through the class hierarchy

Nick Dimiduk created HBASE-24295:
------------------------------------

             Summary: [Chaos Monkey] abstract logging through the class hierarchy
                 Key: HBASE-24295
                 URL: https://issues.apache.org/jira/browse/HBASE-24295
             Project: HBase
          Issue Type: Task
          Components: integration tests
    Affects Versions: 2.3.0
            Reporter: Nick Dimiduk


Running chaos monkey and watching the logs, it's very difficult to tell what actions are actually running. There's lots of shared methods through the class hierarchy that extends from {{abstract class Action}}, and each class comes with its own {{Logger}}. As a result, the logs have useless stuff like

{noformat}
INFO actions.Action: Started regionserver...
{noformat}

Add {{protected abstract Logger getLogger()}} to the class's internal interface, and have the concrete implementations provide their logger.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)