hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-16107) JDBC: HttpClient should retry one more time on NoHttpResponseException
Date Wed, 08 Mar 2017 15:42:38 GMT


Hive QA commented on HIVE-16107:

Here are the results of testing the latest attachment:

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 3 failed/errored test(s), 10334 tests executed
*Failed tests:*
org.apache.hadoop.hive.cli.TestPerfCliDriver.testCliDriver[query14] (batchId=224)
org.apache.hadoop.hive.cli.TestSparkCliDriver.testCliDriver[vector_between_in] (batchId=119)

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
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: 3 tests failed

This message is automatically generated.

ATTACHMENT ID: 12856726 - PreCommit-HIVE-Build

> JDBC: HttpClient should retry one more time on NoHttpResponseException
> ----------------------------------------------------------------------
>                 Key: HIVE-16107
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2, JDBC
>    Affects Versions: 2.0.1, 2.1.1
>            Reporter: Vaibhav Gumashta
>            Assignee: Vaibhav Gumashta
>         Attachments: HIVE-16107.1.patch
> Hive's JDBC client in HTTP transport mode doesn't retry on NoHttpResponseException. We've
seen the exception being thrown to the JDBC end user when used with Knox as the proxy, when
Knox upgraded its jetty version, which has a smaller value for jetty connector idletimeout,
and as a result closes the HTTP connection on server side. The next jdbc query on the client,
throws a NoHttpResponseException. However, subsequent queries reconnect, but the JDBC driver
should ideally handle this by retrying.

This message was sent by Atlassian JIRA

View raw message