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 "Bikas Saha (JIRA)" <ji...@apache.org> on 2013/09/24 21:07:03 UTC

[jira] [Updated] (YARN-986) YARN should have a ClusterId/ServiceId

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

Bikas Saha updated YARN-986:
----------------------------

    Summary: YARN should have a ClusterId/ServiceId  (was: YARN should have a ClusterId/ServiceId that should be used to set the service address for tokens)
    
> YARN should have a ClusterId/ServiceId
> --------------------------------------
>
>                 Key: YARN-986
>                 URL: https://issues.apache.org/jira/browse/YARN-986
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Vinod Kumar Vavilapalli
>
> This needs to be done to support non-ip based fail over of RM. Once the server sets the token service address to be this generic ClusterId/ServiceId, clients can translate it to appropriate final IP and then be able to select tokens via TokenSelectors.
> Some workarounds for other related issues were put in place at YARN-945.

--
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