hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vaibhav Gumashta (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-16172) Switch to a fairness lock to synchronize HS2 thrift client
Date Fri, 10 Mar 2017 17:15:04 GMT

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

Vaibhav Gumashta updated HIVE-16172:
------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.2.0
           Status: Resolved  (was: Patch Available)

Committed. Thanks [~taoli-hwx]

> Switch to a fairness lock to synchronize HS2 thrift client
> ----------------------------------------------------------
>
>                 Key: HIVE-16172
>                 URL: https://issues.apache.org/jira/browse/HIVE-16172
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Tao Li
>            Assignee: Tao Li
>             Fix For: 2.2.0
>
>         Attachments: HIVE-16172.1.patch
>
>
> A synchronized block is used in "org.apache.hive.jdbc.HiveConnection.SynchronizedHandler.invoke(Object,
Method, Object[])" to synchronize the client invocations. The problem is that it does not
guarantee any fairness. One issue we were seeing is that a cancellation request was not able
to be issued to HS2 until all the getOperationStatus() calls are finished from a while loop.
Thus the cancellation cannot take effect.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message