[
https://issues.apache.org/jira/browse/HIVE-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13818036#comment-13818036
]
Hive QA commented on HIVE-5229:
-------------------------------
{color:green}Overall{color}: +1 all checks pass
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12612708/HIVE-5229.5.patch
{color:green}SUCCESS:{color} +1 4598 tests passed
Test results:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/224/testReport
Console output:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/224/console
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12612708
> Better thread management for HiveServer2 async threads
> ------------------------------------------------------
>
> Key: HIVE-5229
> URL: https://issues.apache.org/jira/browse/HIVE-5229
> Project: Hive
> Issue Type: Improvement
> Components: HiveServer2
> Affects Versions: 0.12.0, 0.13.0
> Reporter: Vaibhav Gumashta
> Assignee: Vaibhav Gumashta
> Fix For: 0.13.0
>
> Attachments: HIVE-5229.1.patch, HIVE-5229.2.patch, HIVE-5229.3.patch,
> HIVE-5229.4.patch, HIVE-5229.5.patch
>
>
> [HIVE-4617|https://issues.apache.org/jira/browse/HIVE-4617] provides support
> for async execution in HS2. The async (background) thread pool currently
> creates N threads (server config), which are alive all the time. If all the
> threads in the pool are busy, a new request is added to a blocking queue.
> However, we can improve the strategy by not having all the async (background)
> threads alive when there are no corresponding requests. The async threads
> should die after a certain timeout if there are no new requests to handle.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
