hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-8007) HA: use substitution token for fencing argument
Date Wed, 04 Apr 2012 05:53:20 GMT

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

Todd Lipcon updated HADOOP-8007:

    Attachment: hadoop-8007.txt

Attached patch changes the configuration of the fencing script as follows:

By default, no arguments are passed to the script. This is different than the previous implementation,
but since HA hasn't been in a release yet, I think it's fine to break this.

Instead, users are expected to use the environment to choose whatever arguments they need.
Since we pass the shell command through to bash, environment variables are interpolated.

We already handled passing the configuration through. This patch also adds the ability for
an HAServiceTarget to add additional key/value pairs, which are prefixed with {{target_}}
in the environment. The three passed by the Common code are {{$target_host}}, {{$target_port}},
and {{$target_address}} (which is the same as host:port).

HDFS-3084 will add the NNID and NSID to this map.

I will also file a separate JIRA to update the docs, which unfortunately live in the MapReduce
> HA: use substitution token for fencing argument
> -----------------------------------------------
>                 Key: HADOOP-8007
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8007
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ha
>    Affects Versions: 2.0.0
>            Reporter: Aaron T. Myers
>            Assignee: Todd Lipcon
>         Attachments: hadoop-8007.txt
> Per HADOOP-7983 currently the fencer always passes the target host:port to fence as the
first argument to the fence script, it would be better to use a substitution token. That is
to say, the user would configure "myfence.sh $TARGETHOST foo bar" and Hadoop would substitute
the target. This would allow use of pre-existing scripts that might have a different ordering
of arguments without a wrapper.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message