[
https://issues.apache.org/jira/browse/YARN-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15403712#comment-15403712
]
Sunil G commented on YARN-4091:
-------------------------------
bq.1) Add more detailed diagnostic messages to apps/queues,
bq.2) Merge pending application state into node allocation state.
Yes, this is make sense. we can spin off these improvements.
bq.What do you mean by target state? Could you please explain more?
bq.I think the priority attribute in response could indicate "priority level
0". Do you think it is enough? So we could use "priority skipped"?
Yes. I will try to explain. When an AM container is allocated, the state of app
in the rest o/p is shown as ACCEPTED. Since we already allocated AM container
in this heartbeat, definitely state of app ll become RUNNING/FAILED. So I was
thinking whether it ll be informative to show the target state with the
allocation/rejection and how far it will help the user. This can be
enhancement, by checking use case value, we can choose to do or not do.
> 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.6.patch,
> YARN-4091.preliminary.1.patch, app_activities v2.json, app_activities.json,
> node_activities v2.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]
