You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/07/28 05:17:20 UTC

[jira] [Commented] (OOZIE-2495) change action status from ErrorType.NON_TRANSIENT to TRANSIENT when SSH action occurs AUTH_FAILED occasionally

    [ https://issues.apache.org/jira/browse/OOZIE-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396932#comment-15396932 ] 

Hadoop QA commented on OOZIE-2495:
----------------------------------

Testing JIRA OOZIE-2495

Cleaning local git workspace

----------------------------

{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.    {color:green}+1{color} the patch does not introduce any @author tags
.    {color:green}+1{color} the patch does not introduce any tabs
.    {color:green}+1{color} the patch does not introduce any trailing spaces
.    {color:green}+1{color} the patch does not introduce any line longer than 132
.    {color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.    {color:green}+1{color} the patch does not seem to introduce new RAT warnings
{color:green}+1 JAVADOC{color}
.    {color:green}+1{color} the patch does not seem to introduce new Javadoc warnings
{color:red}-1 COMPILE{color}
.    {color:red}-1{color} HEAD does not compile
.    {color:red}-1{color} patch does not compile
.    {color:green}+1{color} the patch does not seem to introduce new javac warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.    {color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations
.    {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{color:green}+1 DISTRO{color}
.    {color:green}+1{color} distro tarball builds with the patch 

----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/3103/

> change action status from  ErrorType.NON_TRANSIENT to TRANSIENT when SSH action occurs AUTH_FAILED occasionally
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: OOZIE-2495
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2495
>             Project: Oozie
>          Issue Type: Improvement
>          Components: action
>    Affects Versions: 4.2.0
>            Reporter: WangMeng
>         Attachments: OOZIE-2495.01.patch, OOZIE-2495.02.patch
>
>
>     For SSH action ,sometimes it failed  with the following exception :
>    
>     AUTH_FAILED: Not able to perform operation [ssh -o   PasswordAuthentication=no -o KbdInteractiveDevices=no -o StrictHostKeyChecking=no -o ConnectTimeout=20 user@XXX.XX.XX.XXX mkdir -p oozie-oozi/0000067-130808155814753-oozie-oozi-W/sshjob--ssh/ ] | EErrorStream: Warning: Permanently added (RSA) to the list of known hosts. 
>     
>     However , when I execute the same ssh command  by hand  in Oozie server host , it worked.
>     
>     Except  incorrect ssh settings , the reason causing the exception may also be SSH client load is too high when connect, network jitter or others. 
>     Once connect failed, regardless of retry times, oozie will change its status to  ErrorType.NON_TRANSIENT and suspend this action right now.
>     When it occurs ,I think changing the action status from  ErrorType.NON_TRANSIENT to TRANSIENT may be better , this can let action retry automaticly before it be suspended, which can deal with occasionally connect error .



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)