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

Hive QA commented on HIVE-21694:
--------------------------------



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

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 15982 tests passed

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/17153/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/17153/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-17153/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12968048 - PreCommit-HIVE-Build

> Hive driver wait time is fixed for task getting executed in parallel.
> ---------------------------------------------------------------------
>
>                 Key: HIVE-21694
>                 URL: https://issues.apache.org/jira/browse/HIVE-21694
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>    Affects Versions: 4.0.0
>            Reporter: mahesh kumar behera
>            Assignee: mahesh kumar behera
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0
>
>         Attachments: HIVE-21694.01.patch, HIVE-21694.02.patch
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> During a command execution hive driver executes the task in a separate thread 
> if the task to be executed is set as parallel. After starting the task, 
> driver checks if the task has finished execution or not. If the task 
> execution is not finished it waits for 2 seconds before waking up again to 
> check the task status. In case of task with execution time in milliseconds, 
> this wait time can induce substantial overhead. So instead of fixed wait 
> time, exponential backedup sleep time can be used to reduce the sleep 
> overhead. The sleep time can start with 100ms and can increase up to 2 
> seconds doubling on each iteration.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to