hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-1075) AsyncDispatcher and ResourceTrackerService violate serviceStart() semantics
Date Fri, 16 Aug 2013 21:51:47 GMT

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

Steve Loughran updated YARN-1075:

    Priority: Minor  (was: Major)

downgrading to minor as state management logic is not in {{serviceStart()}} and the state
management should now be robust irrespective of what the clients do.
> AsyncDispatcher and ResourceTrackerService violate serviceStart() semantics
> ---------------------------------------------------------------------------
>                 Key: YARN-1075
>                 URL: https://issues.apache.org/jira/browse/YARN-1075
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.1.0-beta
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>            Priority: Minor
>         Attachments: yarn-1075-1.patch
> IIUC, the serviceStart() implementation of services should start local threads/services
first before calling super.serviceStart(). Certain services have this reversed as below -
leading to possibilities where the service would be in state STARTED, but in reality might
not have started yet.
> {code}
> void serviceStart() {
>   super.serviceStart()
>   // service sepecific logic and start operations
> }
> {code}

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

View raw message