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 Sat, 07 Sep 2013 11:52:54 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

[~vinodkv], thanks for your feedback.

I'd like to keep the current behavior that INIT & STOP always come in pairs. It will make
things easier for aux services implementations.

I've modified the IF to check if the current state is not NEW, unless I'm missing something
this addresses the scenario you pointed out:

{code}
      if (container.getCurrentState() 
          != org.apache.hadoop.yarn.api.records.ContainerState.NEW) {
{code}
                
> 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, 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