Junping Du commented on YARN-3350:

Thanks [~wilfreds] for reporting the issue and delivering a quick patch to fix 
A nit comment for the patch:  LOG.debug() can be wrap inside of "if 
(LOG.isDebugEnabled())" which could be faster is LOG is not enabling debug 
I just pinged [~sandyr] on SPARK-5393 as I am curious that why we didn't fix it 
in YARN side earlier. Let's wait for his feedback or we may miss something here.

> YARN RackResolver spams logs with messages at info level
> --------------------------------------------------------
>                 Key: YARN-3350
>                 URL: https://issues.apache.org/jira/browse/YARN-3350
>             Project: Hadoop YARN
>          Issue Type: Improvement
>    Affects Versions: 2.6.0
>            Reporter: Wilfred Spiegelenburg
>            Assignee: Wilfred Spiegelenburg
>         Attachments: YARN-3350.patch, yarn-RackResolver-log.txt
> When you run an application the container logs shows a lot of messages for 
> the RackResolver:
> 2015-03-10 00:58:30,483 INFO [RMCommunicator Allocator] 
> org.apache.hadoop.yarn.util.RackResolver: Resolved node175.example.com to 
> /rack15
> A real world example for a large job was generating 20+ messages in 2 
> milliseconds during a sustained period of time flooding the logs causing the 
> node to run out of disk space.

This message was sent by Atlassian JIRA

Reply via email to