[jira] [Comment Edited] (YARN-9335) [atsv2] Restrict the number of elements held in NM timeline collector when backend is unreachable for async calls
[ https://issues.apache.org/jira/browse/YARN-9335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16795512#comment-16795512 ] Anil Sadineni edited comment on YARN-9335 at 3/19/19 12:31 AM: --- [~abmodi] I observed small correction needed in yarn-default.xml file. queue capacity key name has 'writer' repeated twice. {quote} The setting that decides the capacity of the queue to hold asynchronous timeline entities. yarn.timeline-service.writer.writer.async.queue.capacity 100 {quote} was (Author: sadineni): [~abmodi] I observed small correction needed in yarn-default.xml file. queue capacity key name has 'writer' repeated twice. {{}} {{ The setting that decides the capacity of the queue to hold}} {{ asynchronous timeline entities.}} {{ yarn.timeline-service.-writer-.writer.async.queue.capacity}} {{ 100}} {{}} > [atsv2] Restrict the number of elements held in NM timeline collector when > backend is unreachable for async calls > - > > Key: YARN-9335 > URL: https://issues.apache.org/jira/browse/YARN-9335 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Vrushali C >Assignee: Abhishek Modi >Priority: Major > Attachments: YARN-9335.001.patch, YARN-9335.002.patch > > > For ATSv2 , if the backend is unreachable, the number/size of data held in > timeline collector's memory increases significantly. This is not good for the > NM memory. > Filing jira to set a limit on how many/much should be retained by the > timeline collector in memory in case the backend is not reachable. -- 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
[jira] [Comment Edited] (YARN-9335) [atsv2] Restrict the number of elements held in NM timeline collector when backend is unreachable for async calls
[ https://issues.apache.org/jira/browse/YARN-9335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16795512#comment-16795512 ] Anil Sadineni edited comment on YARN-9335 at 3/19/19 12:28 AM: --- [~abmodi] I observed small correction needed in yarn-default.xml file. queue capacity key name has 'writer' repeated twice. {{}} {{ The setting that decides the capacity of the queue to hold}} {{ asynchronous timeline entities.}} {{ yarn.timeline-service.-writer-.writer.async.queue.capacity}} {{ 100}} {{}} was (Author: sadineni): [~abmodi] I observed small correction needed in yarn-default.xml file. queue capacity key name has 'writer' repeated twice. {quote}{{}} {{ The setting that decides the capacity of the queue to hold}} {{ asynchronous timeline entities.}} {{ yarn.timeline-service.-writer.-writer.async.queue.capacity}} {{ 100}} {{}} {quote} > [atsv2] Restrict the number of elements held in NM timeline collector when > backend is unreachable for async calls > - > > Key: YARN-9335 > URL: https://issues.apache.org/jira/browse/YARN-9335 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Vrushali C >Assignee: Abhishek Modi >Priority: Major > Attachments: YARN-9335.001.patch, YARN-9335.002.patch > > > For ATSv2 , if the backend is unreachable, the number/size of data held in > timeline collector's memory increases significantly. This is not good for the > NM memory. > Filing jira to set a limit on how many/much should be retained by the > timeline collector in memory in case the backend is not reachable. -- 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