hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-910) Allow auxiliary services to listen for container starts and completions
Date Fri, 06 Sep 2013 09:51:53 GMT

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

Alejandro Abdelnur updated YARN-910:
------------------------------------

    Attachment: YARN-910.patch

Thanks Sandy & Vinod. In the latest patch I've took care of all the changes except the
following.

bq. Split AuxServicesEvent into a AuxServicesAppEvent and AuxServicesContainerEvent ? Don't
like nulls like that.

The patch is only adding a new property to the event, container, which is NULL for App events.
All the other NULLs where already there.

Regardless, I've tried refactoring AuxServicesEvent into a AuxServicesAppEvent and AuxServicesContainerEvent.
But the patch gets much bigger as the necessary changes are not  just different names but
the way the AuxiliaryServices handle() would take care of these 2 events. We should introduce
a parent event class for those.

I'd prefer, if you still want to do this break up, to do it as part of another JIRA which
only does the refactoring, without adding new functionality.

                
> Allow auxiliary services to listen for container starts and completions
> -----------------------------------------------------------------------
>
>                 Key: YARN-910
>                 URL: https://issues.apache.org/jira/browse/YARN-910
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager
>    Affects Versions: 2.1.0-beta
>            Reporter: Sandy Ryza
>            Assignee: Alejandro Abdelnur
>         Attachments: YARN-910.patch, YARN-910.patch, YARN-910.patch
>
>
> Making container start and completion events available to auxiliary services would allow
them to be resource-aware.  The auxiliary service would be able to notify a co-located service
that is opportunistically using free capacity of allocation changes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message