You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Chaoyu Tang (JIRA)" <ji...@apache.org> on 2014/07/18 16:19:06 UTC

[jira] [Updated] (HIVE-7445) Improve LOGS for Hive when a query is not able to acquire locks

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

Chaoyu Tang updated HIVE-7445:
------------------------------

    Attachment: HIVE-7445.patch

With this patch, when in debug mode, ZooKeeperHiveLockManager logs out all conflicting locks to a lock which it fails to acquire for a query. The logging looks like:
{code
14/07/18 09:43:08 ERROR ZooKeeperHiveLockManager: Unable to acquire lock for default@sample_07 mode IMPLICIT
14/07/18 09:43:08 DEBUG ZooKeeperHiveLockManager: Requested lock default@sample_07:: mode:IMPLICIT; query:insert into table sample_07 select * from sample_08
14/07/18 09:43:08 DEBUG ZooKeeperHiveLockManager: Conflicting lock to default@sample_07:: mode:IMPLICIT;query:select * from sample_07;queryId:root_20140718064141_439583f9-f281-4d01-ba0c-616523685124;clientIp:10.20.92.233
{code}

> Improve LOGS for Hive when a query is not able to acquire locks
> ---------------------------------------------------------------
>
>                 Key: HIVE-7445
>                 URL: https://issues.apache.org/jira/browse/HIVE-7445
>             Project: Hive
>          Issue Type: Improvement
>          Components: Diagnosability, Logging
>    Affects Versions: 0.13.1
>            Reporter: Chaoyu Tang
>            Assignee: Chaoyu Tang
>            Priority: Minor
>             Fix For: 0.14.0
>
>         Attachments: HIVE-7445.patch
>
>
> Currently the error thrown when you cannot acquire a lock is:
> Error in acquireLocks... 
> FAILED: Error in acquiring locks: Locks on the underlying objects cannot be acquired. retry after some time
> This error is insufficient if the user would like to understand what is blocking them and insufficient from a diagnosability perspective because it is difficult to know what query is blocking the lock acquisition.



--
This message was sent by Atlassian JIRA
(v6.2#6252)