[
https://issues.apache.org/jira/browse/HDFS-15404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shilun Fan updated HDFS-15404:
------------------------------
Component/s: ha
tools
Hadoop Flags: Reviewed
Target Version/s: 3.3.1, 2.10.1, 3.2.2, 3.4.0
Affects Version/s: 3.3.1
2.10.1
3.2.2
3.4.0
> ShellCommandFencer should expose info about source
> --------------------------------------------------
>
> Key: HDFS-15404
> URL: https://issues.apache.org/jira/browse/HDFS-15404
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: ha, tools
> Affects Versions: 3.2.2, 2.10.1, 3.3.1, 3.4.0
> Reporter: Chen Liang
> Assignee: Chen Liang
> Priority: Major
> Fix For: 3.2.2, 2.10.1, 3.3.1, 3.4.0
>
> Attachments: HDFS-15404.001.patch, HDFS-15404.002.patch,
> HDFS-15404.003.patch, HDFS-15404.004.patch, HDFS-15404.005.patch,
> HDFS-15404.006.patch
>
>
> Currently the HA fencing logic in ShellCommandFencer exposes environment
> variable about only the fencing target. i.e. the $target_* variables as
> mentioned in this [document
> page|https://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-hdfs/HDFSHighAvailabilityWithQJM.html]).
>
> But here only the fencing target variables are getting exposed. Sometimes it
> is useful to expose info about the fencing source node. One use case is would
> allow source and target node to identify themselves separately and run
> different commands/scripts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
