hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1068) Add admin support for HA operations
Date Tue, 24 Sep 2013 19:05:04 GMT

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

Bikas Saha commented on YARN-1068:

It would be educative to compare the HAAdmin server start code with existing admin RM server
like the AdminService. I notice 2 things. 
1) AdminService does not use the HAServiceProtocolServerSideTranslatorPB pattern
2) AdminService does something with HADOOP_SECURITY_AUTHORIZATION which is missing in HAAdminService.
This probably defines who has access to perform the admin operations. We will likely need
that for the HAAdmin right?

Having thought about this, it seems to me that this jira is actually blocked by YARN-986.
Without a concept of a logical name how can we expect the CLI etc to find the correct RM address
from configuration? The client conf files would be expected to have entries for all RM instances
and we would need to be able to issue admin commands to any one of them. So we need to be
able to address them via a logical name, right? So the current approach that picks the RM_HA_ADMIN_SERVICE
address does not seem like a viable solution. Similarly, server conf files would need to tell
the server what its logical name is so that it can try to pick and instance specific configurations.
This is precisely why we have the HAAdmin.resolveTarget() method.
Again, it would be educative to look at NNHAServiceTarget for client side and the constructor
for NameNode where is uses the logical name to translate and re-write server side conf.
> Add admin support for HA operations
> -----------------------------------
>                 Key: YARN-1068
>                 URL: https://issues.apache.org/jira/browse/YARN-1068
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>    Affects Versions: 2.1.0-beta
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>              Labels: ha
>         Attachments: yarn-1068-1.patch, yarn-1068-2.patch, yarn-1068-3.patch, yarn-1068-4.patch,
yarn-1068-5.patch, yarn-1068-6.patch, yarn-1068-7.patch, yarn-1068-prelim.patch
> Support HA admin operations to facilitate transitioning the RM to Active and Standby

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