[jira] [Updated] (SAMZA-817) Add metrics to gauge effectiveness of host-affinity solution

["Navina Ramesh (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SAMZA-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Navina Ramesh updated SAMZA-817:
--------------------------------
    Attachment: SAMZA-817-0.patch

RB link for review ->  https://reviews.apache.org/r/40407/

> Add metrics to gauge effectiveness of host-affinity solution
> ------------------------------------------------------------
>
>                 Key: SAMZA-817
>                 URL: https://issues.apache.org/jira/browse/SAMZA-817
>             Project: Samza
>          Issue Type: Sub-task
>    Affects Versions: 0.10.0
>            Reporter: Navina Ramesh
>            Assignee: Navina Ramesh
>         Attachments: SAMZA-817-0.patch
>
>
> We wanted to reduce to container start-up time for jobs that have large change logs. There is no metric to measure this. 
> Additionally, Yarn host-affinity makes a best-effort  to run a container in the requested host. There is no metric to measure this either.
> Proposal:
> Since task store restoration takes up most of the time during a container start-up time, we can measure the time to restore task stores. It may also help identify data distribution among the task stores. To measure "host-affinity" itself on Yarn, we can add a gauge for the ratio of container requests that is successfully matched to the requested host to the total container requests.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)