[
https://issues.apache.org/jira/browse/YARN-10319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17143544#comment-17143544
]
Prabhu Joseph commented on YARN-10319:
--------------------------------------
Thanks [~Tao Yang] for detailed review.
Have addressed all above comments in [^YARN-10319-004.patch] .
bq. The fetching approaches of activities and bulk-activities REST API are
different (asynchronous or synchronous), I think we should elaborate this in
the document.
Have updated the document with below
{code}
The scheduler bulk activities RESTful API can fetch scheduler activities info
recorded for multiple scheduling cycle. This may take time to return as it
internally waits still it records specified activitiesCount.
{code}
> 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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
