Wangda Tan commented on YARN-4091:

By some reason, I replied the JIRA but the comments is not here, sorry for the 
delay :(.

bq. Or we can dump this information as logs.
I would prefer to keep the structured message.

bq. I feel getting information back as REST o/p is more better and we utilize 
this framework in new UI.
Totally agree.

bq. Hence timing of the second REST query is important as the intended node 
heartbeat has to happen (or by the time query comes, more heartbeats from same 
node would have come)
I think we can only store *the next* allocation data once request received, and 
if there's another request comes before the data being fetched, YARN will 
discard the old one.
I think we don't have to keep up-to-date allocation, storing history data in 
memory is not a good idea to me.

> Improvement: Introduce more debug/diagnostics information to detail out 
> scheduler activity
> ------------------------------------------------------------------------------------------
>                 Key: YARN-4091
>                 URL: https://issues.apache.org/jira/browse/YARN-4091
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: capacity scheduler, resourcemanager
>    Affects Versions: 2.7.0
>            Reporter: Sunil G
>            Assignee: Sunil G
>         Attachments: Improvement on debugdiagnostic information - YARN.pdf
> 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

Reply via email to