[jira] [Assigned] (HBASE-18439) Subclasses of o.a.h.h.chaos.actions.Action all use the same logger

2019-11-05 Thread Rabi Kumar K C (Jira) 


 [ 
https://issues.apache.org/jira/browse/HBASE-18439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rabi Kumar K C reassigned HBASE-18439:
--

Assignee: Rabi Kumar K C  (was: Jui-Yu Hsieh)

> 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
>
> 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)

[jira] [Assigned] (HBASE-18439) Subclasses of o.a.h.h.chaos.actions.Action all use the same logger

2017-08-06 Thread Sahil Aggarwal (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HBASE-18439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sahil Aggarwal reassigned HBASE-18439:
--

Assignee: Jui-Yu Hsieh  (was: Sahil Aggarwal)

> 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: Jui-Yu Hsieh
>Priority: Minor
>  Labels: beginner
>
> 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
(v6.4.14#64029)

[jira] [Assigned] (HBASE-18439) Subclasses of o.a.h.h.chaos.actions.Action all use the same logger

2017-08-06 Thread Sahil Aggarwal (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HBASE-18439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sahil Aggarwal reassigned HBASE-18439:
--

Assignee: Sahil Aggarwal

> 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: Sahil Aggarwal
>Priority: Minor
>  Labels: beginner
>
> 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
(v6.4.14#64029)

[jira] [Assigned] (HBASE-18439) Subclasses of o.a.h.h.chaos.actions.Action all use the same logger

2017-08-06 Thread Sahil Aggarwal (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HBASE-18439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sahil Aggarwal reassigned HBASE-18439:
--

Assignee: (was: Sahil Aggarwal)

> 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
>Priority: Minor
>  Labels: beginner
>
> 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
(v6.4.14#64029)

[jira] [Assigned] (HBASE-18439) Subclasses of o.a.h.h.chaos.actions.Action all use the same logger

2017-08-01 Thread Sahil Aggarwal (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HBASE-18439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sahil Aggarwal reassigned HBASE-18439:
--

Assignee: Sahil Aggarwal

> 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: Sahil Aggarwal
>Priority: Minor
>  Labels: beginner
>
> 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
(v6.4.14#64029)