[
https://issues.apache.org/jira/browse/YARN-10319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17162016#comment-17162016
]
Adam Antal commented on YARN-10319:
-----------------------------------
Check the markdown and I could not understand this sentence: "This may take
time to return as it internally waits still it records specified
activitiesCount."
I think "This may take time to return as it internally waits -still it- *until
a certain amount of* records *are generated* specified *by* activitiesCount."
would be more clear.
Besides that it's a +1 from me.
> Record Last N Scheduler Activities from ActivitiesManager
> ---------------------------------------------------------
>
> Key: YARN-10319
> URL: https://issues.apache.org/jira/browse/YARN-10319
> Project: Hadoop YARN
> Issue Type: Improvement
> Affects Versions: 3.3.0
> Reporter: Prabhu Joseph
> Assignee: Prabhu Joseph
> Priority: Major
> Labels: activitiesmanager
> Attachments: Screen Shot 2020-06-18 at 1.26.31 PM.png,
> YARN-10319-001-WIP.patch, YARN-10319-002.patch, YARN-10319-003.patch,
> YARN-10319-004.patch, YARN-10319-005.patch
>
>
> ActivitiesManager records a call flow for a given nodeId or a last call flow.
> This is useful when debugging the issue live where the user queries with
> right nodeId. But capturing last N scheduler activities during the issue
> period can help to debug the issue offline.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
