[
https://issues.apache.org/jira/browse/HBASE-18439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Hentschel resolved HBASE-18439.
-----------------------------------
Fix Version/s: 2.2.3
2.1.8
1.3.7
1.4.12
1.6.0
2.3.0
3.0.0
Hadoop Flags: Reviewed
Resolution: Fixed
> Subclasses of o.a.h.h.chaos.actions.Action all use the same logger
> ------------------------------------------------------------------
>
> Key: HBASE-18439
> URL: https://issues.apache.org/jira/browse/HBASE-18439
> Project: HBase
> Issue Type: Bug
> Components: integration tests
> Reporter: Mike Drob
> Assignee: Rabi Kumar K C
> Priority: Minor
> Labels: beginner
> Fix For: 3.0.0, 2.3.0, 1.6.0, 1.4.12, 1.3.7, 2.1.8, 2.2.3
>
>
> A bunch of the actions all use the same logger inherited from the super
> class. We should have them declare distinct loggers, either each one in class
> or perhaps we can do something dynamically like
> {{LogFactory.getLogger(MethodHandles.lookup().lookupClass()}} and drop the
> static modifier on the log field.
> I'm not sure that exact incantation would actually work, but the
> MethodHandles approach in general is how logger resolution happens in Solr
> and it actually works out pretty well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
