Ray Chiang commented on YARN-2868:

Addressing the doubts:

1) It could be added to both.  I'm not as familiar with CS, but I can certainly 
look into it.
2) It's somewhat handy for debugging and there was a much earlier version that 
was recording from within different methods, so I had to store it somewhere.  I 
was keeping it around in case the metric start/stop points needed to be changed 

And addressing the comments:

1) Yeah, I could remove initialized.  My next step was to measure all the other 
container allocations (i.e. after the first) as a separate metric and I was 
thinking I would use it somehow.
2) Argh.  That's probably left over from when I was changing from measuring all 
queues to measuring per-queue.  I'll fix that.

Thanks for the sharp eyes.

> Add metric for initial container launch time
> --------------------------------------------
>                 Key: YARN-2868
>                 URL: https://issues.apache.org/jira/browse/YARN-2868
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Ray Chiang
>            Assignee: Ray Chiang
>              Labels: metrics, supportability
>         Attachments: YARN-2868-01.patch, YARN-2868.002.patch, 
> YARN-2868.003.patch, YARN-2868.004.patch, YARN-2868.005.patch, 
> YARN-2868.006.patch
> Add a metric to measure the latency between "starting container allocation" 
> and "first container actually allocated".

This message was sent by Atlassian JIRA

Reply via email to