[
https://issues.apache.org/jira/browse/ACCUMULO-3617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14487748#comment-14487748
]
Christopher Tubbs commented on ACCUMULO-3617:
---------------------------------------------
The waffling is due to the fact that while it's trivial to remove all such log
messages, it is slightly more complex to nuke only the unloadTablet message.
We'd have to add conditional checks to filter which message type it is, and log
them if they are not the spammy unloadTablet one.
It's not clear to me that those conditional checks to single out the
unloadTablet message from the others is worthwhile.
> 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.8.0, 1.7.1
>
>
> 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)
