[jira] [Updated] (HIVE-21694) Hive driver wait time is fixed for task getting executed in parallel.

2019-05-07 Thread mahesh kumar behera (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-21694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

mahesh kumar behera updated HIVE-21694:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

02.patch is Committed to master. Thanks [~sankarh] for review.

> 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: 20m
>  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 the execution thread can 
> call notify to interrupt the wait call. This will make sure that the next 
> thread execution can start immediately.



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


[jira] [Updated] (HIVE-21694) Hive driver wait time is fixed for task getting executed in parallel.

2019-05-07 Thread mahesh kumar behera (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-21694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

mahesh kumar behera updated HIVE-21694:
---
Description: 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 the execution thread can 
call notify to interrupt the wait call. This will make sure that the next 
thread execution can start immediately.  (was: 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.)

> 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 the execution thread can 
> call notify to interrupt the wait call. This will make sure that the next 
> thread execution can start immediately.



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


[jira] [Updated] (HIVE-21694) Hive driver wait time is fixed for task getting executed in parallel.

2019-05-07 Thread mahesh kumar behera (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-21694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

mahesh kumar behera updated HIVE-21694:
---
Attachment: HIVE-21694.02.patch

> 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)


[jira] [Updated] (HIVE-21694) Hive driver wait time is fixed for task getting executed in parallel.

2019-05-07 Thread mahesh kumar behera (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-21694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

mahesh kumar behera updated HIVE-21694:
---
Status: Open  (was: Patch Available)

> 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)


[jira] [Updated] (HIVE-21694) Hive driver wait time is fixed for task getting executed in parallel.

2019-05-07 Thread mahesh kumar behera (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-21694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

mahesh kumar behera updated HIVE-21694:
---
Status: Patch Available  (was: Open)

> 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)


[jira] [Updated] (HIVE-21694) Hive driver wait time is fixed for task getting executed in parallel.

2019-05-07 Thread mahesh kumar behera (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-21694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

mahesh kumar behera updated HIVE-21694:
---
Attachment: (was: HIVE-21694.01.patch)

> 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
>
>  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)


[jira] [Updated] (HIVE-21694) Hive driver wait time is fixed for task getting executed in parallel.

2019-05-07 Thread mahesh kumar behera (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-21694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

mahesh kumar behera updated HIVE-21694:
---
Status: Patch Available  (was: Open)

> 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
>
>  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)


[jira] [Updated] (HIVE-21694) Hive driver wait time is fixed for task getting executed in parallel.

2019-05-07 Thread mahesh kumar behera (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-21694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

mahesh kumar behera updated HIVE-21694:
---
Attachment: HIVE-21694.01.patch

> 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
>
>  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)


[jira] [Updated] (HIVE-21694) Hive driver wait time is fixed for task getting executed in parallel.

2019-05-07 Thread mahesh kumar behera (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-21694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

mahesh kumar behera updated HIVE-21694:
---
Status: Open  (was: Patch Available)

> 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
>
>  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)


[jira] [Updated] (HIVE-21694) Hive driver wait time is fixed for task getting executed in parallel.

2019-05-06 Thread ASF GitHub Bot (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-21694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated HIVE-21694:
--
Labels: pull-request-available  (was: )

> 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
>
>
> 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)


[jira] [Updated] (HIVE-21694) Hive driver wait time is fixed for task getting executed in parallel.

2019-05-06 Thread mahesh kumar behera (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-21694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

mahesh kumar behera updated HIVE-21694:
---
Attachment: HIVE-21694.01.patch

> 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
> Fix For: 4.0.0
>
> Attachments: HIVE-21694.01.patch
>
>
> 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)


[jira] [Updated] (HIVE-21694) Hive driver wait time is fixed for task getting executed in parallel.

2019-05-06 Thread mahesh kumar behera (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-21694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

mahesh kumar behera updated HIVE-21694:
---
Status: Patch Available  (was: Open)

> 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
> Fix For: 4.0.0
>
> Attachments: HIVE-21694.01.patch
>
>
> 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)


[jira] [Updated] (HIVE-21694) Hive driver wait time is fixed for task getting executed in parallel.

2019-05-05 Thread mahesh kumar behera (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-21694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

mahesh kumar behera updated HIVE-21694:
---
Summary: Hive driver wait time is fixed for task getting executed in 
parallel.  (was: Hive driver waiting time is fixed for task getting executed in 
parallel.)

> 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
> Fix For: 4.0.0
>
>
> 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)