hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-4865) HiveLockObjects: Unlocking retries/times out when query contains ":"
Date Tue, 16 Jul 2013 20:52:48 GMT

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

Hive QA commented on HIVE-4865:
-------------------------------



{color:green}Overall:{color}: +1 all checks pass

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

{color:green}SUCCESS:{color} +1 all tests passed

Test results: https://builds.apache.org/job/Hive-Precommit-trunk-hadoop1-ptest/6/testReport
Console output: https://builds.apache.org/job/Hive-Precommit-trunk-hadoop1-ptest/6/console
Executing org.apache.hive.ptest.execution.CleanupPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase

This message is automatically generated.
                
> HiveLockObjects: Unlocking retries/times out when query contains ":"
> --------------------------------------------------------------------
>
>                 Key: HIVE-4865
>                 URL: https://issues.apache.org/jira/browse/HIVE-4865
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Gunther Hagleitner
>            Assignee: Gunther Hagleitner
>         Attachments: HIVE-4865.1.patch, HIVE-4865.2.patch
>
>
> The full query string is part of the HiveLockObject. If that string contains a ":" the
data fetched from Zookeeper will not be correctly parsed. This causes locks that have been
released to not be removed from the lock list.
> The result is that the same path will be removed from zookeeper multiple times. This
fails and causes a very long retry loop.
> timestamp_1.q & timestamp_2.q take an hour right now. The reason is just this problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message