You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "Navis (JIRA)" <ji...@apache.org> on 2014/02/20 02:09:31 UTC

[jira] [Commented] (HIVE-6464) Test configuration: reduce the duration for which lock attempts are retried

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

Navis commented on HIVE-6464:
-----------------------------

+1

> Test configuration: reduce the duration for which lock attempts are retried
> ---------------------------------------------------------------------------
>
>                 Key: HIVE-6464
>                 URL: https://issues.apache.org/jira/browse/HIVE-6464
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Thejas M Nair
>            Assignee: Thejas M Nair
>         Attachments: HIVE-6464.1.patch
>
>
> Lock attempts are being done for 60 seconds * 100 before it gives up. Most tests attempt to disable locking but sometimes don't do it correctly and changes can cause the locking to kick in. Locking fails, (at least in the HS2 related tests) because of problems in creating the zookeeper entries in test mode. When locking attempt kicks in and that fails, it can end up waiting for 6000 seconds before failing.
> As the tests are not trying to test parallel locking, there is no reason to wait this long in the tests. 
> We should update hive-site.xml used by tests for smaller duration.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)