Return-Path: X-Original-To: apmail-hive-dev-archive@www.apache.org Delivered-To: apmail-hive-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 715EC108C5 for ; Tue, 16 Jul 2013 08:16:53 +0000 (UTC) Received: (qmail 64280 invoked by uid 500); 16 Jul 2013 08:16:51 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 63947 invoked by uid 500); 16 Jul 2013 08:16:50 -0000 Mailing-List: contact dev-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list dev@hive.apache.org Received: (qmail 63883 invoked by uid 500); 16 Jul 2013 08:16:50 -0000 Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org Received: (qmail 63874 invoked by uid 99); 16 Jul 2013 08:16:49 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Jul 2013 08:16:49 +0000 Date: Tue, 16 Jul 2013 08:16:49 +0000 (UTC) From: "Gunther Hagleitner (JIRA)" To: hive-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HIVE-4865) HiveLockObjects: Unlocking retries/times out when query contains ":" MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Gunther Hagleitner created HIVE-4865: ---------------------------------------- Summary: 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 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