[
https://issues.apache.org/jira/browse/YARN-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15402484#comment-15402484
]
Chen Ge edited comment on YARN-4091 at 8/1/16 5:45 PM:
-------------------------------------------------------
Thanks [~sunilg] for the reminder.
In test report, NullPointerException and missing REJECTED diagnostic has been
addressed.
For this one,
*"State of application_1469802642816_0004 after allocation will be RUNNING.
Could we*
*propose something here that what can be target state since container is
allocated (failed*
*or running)"*
What do you mean by target state? Could you please explain more?
For this one,
*"priority skipped" ⇒ "Skipped allocation at priority level 0"*
I think the priority attribute in response could indicate "priority level 0".
Do you think it is enough? So we could use "priority skipped"?
Thank you very much for improvements.
was (Author: chenge):
Thanks for the reminder.
In test report, NullPointerException and missing REJECTED diagnostic has been
addressed.
For this one,
*"State of application_1469802642816_0004 after allocation will be RUNNING.
Could we*
*propose something here that what can be target state since container is
allocated (failed*
*or running)"*
What do you mean by target state? Could you please explain more?
For this one,
*"priority skipped" ⇒ "Skipped allocation at priority level 0"*
I think the priority attribute in response could indicate "priority level 0".
Do you think it is enough? So we could use "priority skipped"?
Thank you very much for improvements.
> Add REST API to retrieve scheduler activity
> -------------------------------------------
>
> Key: YARN-4091
> URL: https://issues.apache.org/jira/browse/YARN-4091
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: capacity scheduler, resourcemanager
> Affects Versions: 2.7.0
> Reporter: Sunil G
> Assignee: Chen Ge
> Attachments: Improvement on debugdiagnostic information - YARN.pdf,
> SchedulerActivityManager-TestReport v2.pdf,
> SchedulerActivityManager-TestReport.pdf, YARN-4091-design-doc-v1.pdf,
> YARN-4091.1.patch, YARN-4091.2.patch, YARN-4091.3.patch, YARN-4091.4.patch,
> YARN-4091.5.patch, YARN-4091.5.patch, YARN-4091.preliminary.1.patch,
> app_activities.json, node_activities.json
>
>
> As schedulers are improved with various new capabilities, more configurations
> which tunes the schedulers starts to take actions such as limit assigning
> containers to an application, or introduce delay to allocate container etc.
> There are no clear information passed down from scheduler to outerworld under
> these various scenarios. This makes debugging very tougher.
> This ticket is an effort to introduce more defined states on various parts in
> scheduler where it skips/rejects container assignment, activate application
> etc. Such information will help user to know whats happening in scheduler.
> Attaching a short proposal for initial discussion. We would like to improve
> on this as we discuss.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
