[
https://issues.apache.org/jira/browse/HADOOP-11119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14513527#comment-14513527
]
Vinayakumar B commented on HADOOP-11119:
----------------------------------------
bq. Basically, interactive commands shouldn't show the message but daemons
should. Totally eliminating the message isn't going to work.
I think, moving the log message from {{TrashPolicyDefault#initialize(..)}} to
{{TrashPolicyDefault.Emptier}} constructor would do the trick. As Emptier
would be running only in the ActiveNamenode and this Emptier constuctor would
be called only in NN. So client will no longer have the log message.
What you say [~aw] ?
> TrashPolicyDefault init pushes messages to command line
> -------------------------------------------------------
>
> Key: HADOOP-11119
> URL: https://issues.apache.org/jira/browse/HADOOP-11119
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Allen Wittenauer
> Assignee: Brahma Reddy Battula
> Priority: Minor
> Attachments: HADOOP-11119.patch
>
>
> During a fresh install of trunk:
> {code}
> aw-mbp-work:hadoop-3.0.0-SNAPSHOT aw$ bin/hadoop fs -put /etc/hosts /tmp
> aw-mbp-work:hadoop-3.0.0-SNAPSHOT aw$ bin/hadoop fs -rm /tmp/hosts
> 14/09/23 13:05:46 INFO fs.TrashPolicyDefault: Namenode trash configuration:
> Deletion interval = 0 minutes, Emptier interval = 0 minutes.
> Deleted /tmp/hosts
> {code}
> The info message for the Namenode trash configuration isn't very useful.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
