[
https://issues.apache.org/jira/browse/HIVE-6268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886504#comment-13886504
]
Hive QA commented on HIVE-6268:
-------------------------------
{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/12625972/HIVE-6268.3.patch
{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 4972 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestMinimrCliDriver.testCliDriver_bucket_num_reducers
{noformat}
Test results:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/1110/testReport
Console output:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/1110/console
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: 12625972
> Network resource leak with HiveClientCache when using HCatInputFormat
> ---------------------------------------------------------------------
>
> Key: HIVE-6268
> URL: https://issues.apache.org/jira/browse/HIVE-6268
> Project: Hive
> Issue Type: Bug
> Components: HCatalog
> Affects Versions: 0.12.0
> Reporter: Sushanth Sowmyan
> Assignee: Sushanth Sowmyan
> Attachments: HIVE-6268.2.patch, HIVE-6268.3.patch, HIVE-6268.patch
>
>
> HCatInputFormat has a cache feature that allows HCat to cache hive client
> connections to the metastore, so as to not keep reinstantiating a new hive
> server every single time. This uses a guava cache of hive clients, which only
> evicts entries from cache on the next write, or by manually managing the
> cache.
> So, in a single threaded case, where we reuse the hive client, the cache
> works well, but in a massively multithreaded case, where each thread might
> perform one action, and then is never used, there are no more writes to the
> cache, and all the clients stay alive, thus keeping ports open.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
