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

Hive QA commented on HIVE-8901:
-------------------------------



{color:red}Overall{color}: -1 at least one tests failed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12682017/HIVE-8901.1.patch

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 6647 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestMiniTezCliDriver.testCliDriver_optimize_nullscan
{noformat}

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1829/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1829/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1829/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 1 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12682017 - PreCommit-HIVE-TRUNK-Build

> increase retry attempt, interval on metastore database errors
> -------------------------------------------------------------
>
>                 Key: HIVE-8901
>                 URL: https://issues.apache.org/jira/browse/HIVE-8901
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Thejas M Nair
>            Assignee: Thejas M Nair
>             Fix For: 0.15.0
>
>         Attachments: HIVE-8901.1.patch
>
>
> The current defaults of hive.hmshandler.retry.attempts=1 and 
> hive.hmshandler.retry.interval=1s are very small. In some cases one retry is 
> not sufficient for successful command execution.
>  
> I have seen cases, specially after metastore being idle for sometime, when it 
> takes 2 attempts for the db action to succeed. In this case, it as a 
> Communications link failure/connection lost error.



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

Reply via email to