[OOZIE-3183] Better logging for SshActionExecutor and extended HA capability when calling to remote host

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0.0b1
• Fix Version/s: 5.0.0
• Component/s: action
• Assignee: Andras Piros
• Reporter: Andras Piros
• Created: 14/Feb/18 01:47
• Updated: 27/Sep/18 18:30
• Resolved: 14/Feb/18 14:52

Description

In some High Availability environments, when an SSH action's SshActionExecutor#start() runs on another node than SshActionExecutor#check(), it can happen that due to network bandwidth reasons calling Process#exitValue() is not enough - but calling Process#waitFor() is better.

Also, for better error root cause analysis, enhance logging along SshActionExecutor for the critical parts.

Issue Links

• is related to: OOZIE-3354 [core] [SSH action] SSH action gets hung