You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Sandy Ryza (JIRA)" <ji...@apache.org> on 2014/01/04 21:15:51 UTC

[jira] [Commented] (YARN-1558) After apps are moved across queues, store new queue info in the RM state store

    [ https://issues.apache.org/jira/browse/YARN-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862404#comment-13862404 ] 

Sandy Ryza commented on YARN-1558:
----------------------------------

Right.  Updated the title and description with more info.  I don't think this will be covered by general configuration management across restarts, but let me know if I'm missing something.

> After apps are moved across queues, store new queue info in the RM state store
> ------------------------------------------------------------------------------
>
>                 Key: YARN-1558
>                 URL: https://issues.apache.org/jira/browse/YARN-1558
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: scheduler
>            Reporter: Sandy Ryza
>
> The result of moving an app to a new queue should persist across RM restarts.  This will require updating the ApplicationSubmissionContext, the single source of truth upon state recovery, with the new queue info.
> There will be a brief window after the move completes before the move is stored.  If the RM dies during this window, the recovered RM will include the old queue info.  Schedulers should be resilient to this situation.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)