[
https://issues.apache.org/jira/browse/MAPREDUCE-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728619#action_12728619
]
Sreekanth Ramakrishnan commented on MAPREDUCE-732:
--------------------------------------------------
We log everytime when node changes it health status. But currently when a node
becomes unhealthy, every subsequent heart beat we log "Adding blacklisted
reason for tracker :". This has to be changed as we might end up logging a line
per blacklisted tracker every heartbeat, filling up the log files.
The logging of the change in health status is done in line number 648 and 623
of {{JobTracker}}
> node health check script should not log "UNHEALTHY" status for every
> heartbeat in INFO mode
> -------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-732
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-732
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 0.21.0
> Reporter: Ramya R
> Assignee: Sreekanth Ramakrishnan
> Priority: Minor
> Fix For: 0.21.0
>
> Attachments: mapreduce-732.patch
>
>
> Currently, when a TT is blacklisted by the node health check script, for
> every heartbeat a message such as the following is being logged.
> {noformat}
> <date> <time> INFO org.apache.hadoop.mapred.JobTracker: Adding blacklisted
> reason for tracker : <blacklisted TT> Reason for blacklisting is :
> NODE_UNHEALTHY
> {noformat}
> Due to this, the the JT logs fill up rapidly clogging the logdirs. Hence this
> message should be logged in DEBUG mode instead of INFO mode.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
