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

Vrushali C commented on YARN-8156:
----------------------------------

Thanks [~charanh] for the patch! It looks good, but I think let's increase the 
default interval to 60 seconds. It is configurable anyways, so should not be an 
issue that it might appear too big to some.  In the default config case, it 
will then take care of most situations of race conditions of entities coming in 
after the collector has been removed. 

> Increase the default value of 
> yarn.timeline-service.app-collector.linger-period.ms
> ----------------------------------------------------------------------------------
>
>                 Key: YARN-8156
>                 URL: https://issues.apache.org/jira/browse/YARN-8156
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Rohith Sharma K S
>            Assignee: Charan Hebri
>            Priority: Major
>         Attachments: YARN-8156.001.patch
>
>
> The default value of *yarn.timeline-service.app-collector.linger-period.ms* 
> is 1 sec which is very low. In production cluster, we observe that most of 
> the entity information is not published because of 1sec linger period. 
> I would suggest to increase the default value to either 10sec or 30sec or 60 
> sec. As far as I have seen, 10sec should be sufficient since node heartbeat 
> period is 3 sec by default, all NM gets request to stop the application. 
>  cc:/ [~haibo.chen] [~vrushalic]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to