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:23:20 UTC
[jira] [Commented] (OOZIE-2568) SSH action pretends to retry
automaticly when it failed
[ https://issues.apache.org/jira/browse/OOZIE-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396942#comment-15396942 ]
Hadoop QA commented on OOZIE-2568:
----------------------------------
Testing JIRA OOZIE-2568
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}
. Tests run: 1791
. Tests failed: 5
. Tests errors: 2
. The patch failed the following testcases:
. testPigScript(org.apache.oozie.action.hadoop.TestPigMainWithOldAPI)
. testPigScript(org.apache.oozie.action.hadoop.TestPigMain)
. testEmbeddedPigWithinPython(org.apache.oozie.action.hadoop.TestPigMain)
. testPig_withNullExternalID(org.apache.oozie.action.hadoop.TestPigMain)
. testMain(org.apache.oozie.action.hadoop.TestHiveMain)
{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/3099/
> SSH action pretends to retry automaticly when it failed
> --------------------------------------------------------
>
> Key: OOZIE-2568
> URL: https://issues.apache.org/jira/browse/OOZIE-2568
> Project: Oozie
> Issue Type: Bug
> Components: core
> Affects Versions: 4.2.0
> Reporter: WangMeng
> Attachments: OOZIE-2568.01.patch
>
>
> There is a bug in automaticly retry of SSH action :
> For example:
> I have configed the following retry property :
> {code}
> <name>oozie.service.LiteWorkflowStoreService.user.retry.error.code.ext</name>
> <value>ALL</value>
> {code}
> And my SSH action is :
> {code}
> <action name="ssh-afbb" retry-max="3" retry-interval="1">
> <ssh xmlns="uri:oozie:ssh-action:0.1">
> <host>wangmeng@XXXX</host>
> <command>sh /data/wangmeng/hue_sh4.sh</command>
> <capture-output/>
> </ssh>
> <ok to="End"/>
> <error to="Kill"/>
> </action>
> {code}
> When this action failed，it pretends to retry automaticly according to logs. Such as :
> {code}
> Start action [0000000-160612140701137-oozie-oozi-W@ssh-afbb] with user-retry state : userRetryCount [1], userRetryMax [3], userRetryInterval [1]
> {code}
> However, it does not actually re run the above command "sh /data/wangmeng/hue_sh4.sh".
> The reason is : if the previous PID exists in XXXX.pid file of this SSH action’s log dir , without checking this PID process is finished or not , SSH action will not launch a new process to rerun command. And in my tests , I find this PID process have finished when Oozie rerun this action.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)