accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3758) Fate operations should use their own logger
Date Wed, 29 Apr 2015 02:02:06 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14518564#comment-14518564
] 

Christopher Tubbs commented on ACCUMULO-3758:
---------------------------------------------

After further examination, it looks like there's many places where classes are using a logger
identified as a different class. This is unusual, and can be misleading in examining the logs.
Most of these are obvious copy/paste errors, but some may have occurred due to refactoring
internal code.

> Fate operations should use their own logger
> -------------------------------------------
>
>                 Key: ACCUMULO-3758
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3758
>             Project: Accumulo
>          Issue Type: Bug
>          Components: master
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>            Priority: Minor
>              Labels: summit2015
>             Fix For: 1.7.0
>
>
> MasterRepo's Logger appears to be shared among all subclasses. Subclasses should use
their own Logger, so the logs are more informative.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message