Fencer implementation that uses PowerShell to fence a remote component.
HA: fencing mechanism
Fix ShellCommandFencer to work on Windows
Enhancements to support Hadoop on Windows Server and Windows Azure environments
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11644 (See https://builds.apache.org/job/Hadoop-trunk-Commit/11644/)
HADOOP-14309. Add PowerShell NodeFencer. Contributed by Inigo Goiri (cdouglas: rev 31cf480d6520e259f2a7f29de64ef4c5b5a50142)
Chris Douglas, thanks for the review and the commit.
+1 I committed this. Thanks, Inigo
Thanks Chris Douglas for the review.
The filter is kind of tricky because it should parse the whole class name which is passed to java.exe to start.
In this case, I'm leaving the option for the administrator to set whatever in the CommandLine filter.
The current SSH bases it on the port number.
I'll fix the findbugs and the deleteOnExit.
Looks reasonable, given my rudimentary PowerShell. Does the commandline include some unique string? Should this fail if this matches more than one process at the remote host?
+1 if the findbugs warning is fixed. This could also call deleteOnExit on the temp file instance.
This message was automatically generated.
To enable the fencing mechanism for HDFS HA, one could set:
Fencer method that uses PowerShell to remotely connect to a machine and kill the required process.