You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2015/03/18 19:30:38 UTC

[jira] [Commented] (ACCUMULO-3617) unloadTablet log message in TabletServer is spammy w/o purpose

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

Christopher Tubbs commented on ACCUMULO-3617:
---------------------------------------------

The same log statement which logs this message logs all the other incoming requests at the debug level also. It's in a "checkPermission" method, so it's trying to provide some auditing information for debugging permissions checks. Should we just move these all to trace or should we remove all of them? Or, should the unloadTablet message be specifically suppressed and the others shown?

> unloadTablet log message in TabletServer is spammy w/o purpose
> --------------------------------------------------------------
>
>                 Key: ACCUMULO-3617
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3617
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: tserver
>    Affects Versions: 1.5.2, 1.6.2
>            Reporter: Josh Elser
>            Priority: Minor
>              Labels: newbie
>             Fix For: 1.7.0
>
>
> Looking at TabletServer logs, the following message can be overwhelming:
> {noformat}
> 2015-02-24 01:57:34,723 [tserver.TabletServer] DEBUG: Got unloadTablet message from user: !SYSTEM
> {noformat}
> This message alone tells us nothing (no context about the tablet(s) requested to be unloaded, only that there was a request to unload a tablet), and can appear in the log upwards of 20 times a millisecond.
> It might be better if the TabletServer did...
> * Batched log messages "N unloadTablet requests in $duration"
> * Include extent to unload
> * Kill the log message entirely.



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