hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xuan Gong (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1611) Make admin refresh of configuration work across RM failover
Date Wed, 29 Jan 2014 22:00:09 GMT

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

Xuan Gong commented on YARN-1611:

Thanks for comments, [~sandyr] 

bq. Just took a quick look at the patch. Right now we have a nice one way relationship where
configs affect the services, but the services do not affect configs. The patch appears to
have the RM deleting and uploading files to the remote config directory, which makes me nervous.
Would it make sense for the admin to be responsible for placing configs in the remote dir,
and the RMs just be responsible for pulling them down?

Yes, you are right. Will remove upload and deleting file from RemoteConfiguration functionality.

bq. Will the existing way of doing things (writing files to disk for RMs and calling refresh
on both) still be supported?

Yes, it is still supported. In HA case, if there is no remote configuration, it will give
the warning message. 

bq. Will the remote configuration be supported for the non-HA case?

Currently, no. This is for HA case. 

> Make admin refresh of configuration work across RM failover
> -----------------------------------------------------------
>                 Key: YARN-1611
>                 URL: https://issues.apache.org/jira/browse/YARN-1611
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Xuan Gong
>            Assignee: Xuan Gong
>         Attachments: YARN-1611.1.patch, YARN-1611.2.patch, YARN-1611.2.patch, YARN-1611.3.patch,
YARN-1611.3.patch, YARN-1611.4.patch
> Currently, If we do refresh* for a standby RM, it will failover to the current active
RM, and do the refresh* based on the local configuration file of the active RM. 

This message was sent by Atlassian JIRA

View raw message