[
https://issues.apache.org/jira/browse/HIVE-10143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14387331#comment-14387331
]
Hive QA commented on HIVE-10143:
--------------------------------
{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/12708211/HIVE-10143.1-spark.patch
{color:red}ERROR:{color} -1 due to 4 failed/errored test(s), 8710 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_nonmr_fetch
org.apache.hadoop.hive.cli.TestSparkCliDriver.testCliDriver_union31
org.apache.hadoop.hive.cli.TestSparkCliDriver.testCliDriver_union_remove_22
org.apache.hadoop.hive.cli.TestSparkCliDriver.testCliDriver_union_remove_6_subq
{noformat}
Test results:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-SPARK-Build/814/testReport
Console output:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-SPARK-Build/814/console
Test logs:
http://ec2-50-18-27-0.us-west-1.compute.amazonaws.com/logs/PreCommit-HIVE-SPARK-Build-814/
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: 4 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12708211 - PreCommit-HIVE-SPARK-Build
> HS2 fails to clean up Spark client state on timeout [Spark Branch]
> ------------------------------------------------------------------
>
> Key: HIVE-10143
> URL: https://issues.apache.org/jira/browse/HIVE-10143
> Project: Hive
> Issue Type: Bug
> Components: Spark
> Affects Versions: spark-branch
> Reporter: Marcelo Vanzin
> Assignee: Marcelo Vanzin
> Attachments: HIVE-10143.1-spark.patch
>
>
> When a new client is registered with the Spark client and fails to connect
> back in time, the code will time out the future and HS2 will give up on that
> client. But the RSC backend does not clean up all the state, and the client
> is still allowed to connect back. That can lead to the client staying alive
> indefinitely and holding on to cluster resources, since HS2 doesn't know it's
> alive but the connection still exists.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
