[
https://issues.apache.org/jira/browse/OOZIE-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16744198#comment-16744198
]
Hadoop QA commented on OOZIE-3422:
----------------------------------
Testing JIRA OOZIE-3422
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 star imports
. {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} Javadoc generation succeeded with the patch
. {color:green}+1{color} the patch does not seem to introduce new Javadoc
warning(s)
. {color:orange}WARNING{color}: the current HEAD has 100 Javadoc warning(s)
{color:green}+1 COMPILE{color}
. {color:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/git].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [core].
{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:green}+1 TESTS{color}
. Tests run: 3110
. {color:orange}Tests failed at first run:{color}
TestPurgeXCommand#testPurgeableBundleUnpurgeableCoordinatorUnpurgeableWorkflow
TestPurgeXCommand#testPurgeableWorkflowPurgeableSubWorkflowPurgeableSubSubWorkflow
. For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{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}
{color:red}. There is at least one warning, please check{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/PreCommit-OOZIE-Build/972/
> Enhance logging of Oozie client connecting to the Oozie server
> --------------------------------------------------------------
>
> Key: OOZIE-3422
> URL: https://issues.apache.org/jira/browse/OOZIE-3422
> Project: Oozie
> Issue Type: Improvement
> Affects Versions: 5.1.0
> Reporter: Andras Salamon
> Assignee: Andras Salamon
> Priority: Major
> Attachments: OOZIE-3422-01.patch
>
>
> When the Oozie client tries to connect to the server and fails the error
> message is not always helpful.
> {noformat}
> $ oozie jobs -oozie http://thisisawrongurl
>
>
>
>
> Error: IO_ERROR : java.io.IOException: Error while connecting Oozie server.
> No of retries = 1. Exception = thisisawrongurl
> {noformat}
> A few examples with more helpful error messages:
> {noformat}
> $ oozie jobs -oozie http://localhost:11001
> Connection exception has occurred [ java.net.ConnectException Connection
> refused (Connection refused) ]. Trying after 1 sec. Retry count = 1
> Connection exception has occurred [ java.net.ConnectException Connection
> refused (Connection refused) ]. Trying after 2 sec. Retry count = 2
> Connection exception has occurred [ java.net.ConnectException Connection
> refused (Connection refused) ]. Trying after 4 sec. Retry count = 3
> Connection exception has occurred [ java.net.ConnectException Connection
> refused (Connection refused) ]. Trying after 8 sec. Retry count = 4
> Error: IO_ERROR : java.io.IOException: Error while connecting Oozie server.
> No of retries = 4. Exception = Connection refused (Connection refused)
> $ oozie jobs -oozie http://localhost:11000/oozietypo
> Error: IO_ERROR : java.io.IOException: Error while connecting Oozie server.
> No of retries = 1. Exception = Could not authenticate, Authentication failed,
> status: 404, message: Not Found
> {noformat}
> It is not enought to print out the {{getMessage()}} of the {{Exception}}, we
> should also print out the full stack trace in the
> {{ConnectionRetriableClient}} class.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
