You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Andras Piros (JIRA)" <ji...@apache.org> on 2018/02/14 01:48:00 UTC
[jira] [Created] (OOZIE-3183) Better logging for SshActionExecutor
and extended HA capability when calling to remote host
Andras Piros created OOZIE-3183:
-----------------------------------
Summary: Better logging for SshActionExecutor and extended HA capability when calling to remote host
Key: OOZIE-3183
URL: https://issues.apache.org/jira/browse/OOZIE-3183
Project: Oozie
Issue Type: Improvement
Components: action
Affects Versions: 5.0.0b1
Reporter: Andras Piros
Assignee: Andras Piros
Fix For: 5.0.0
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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)