hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thejas M Nair (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-6464) Test configuration: reduce the duration for which lock attempts are retried
Date Fri, 21 Feb 2014 21:03:20 GMT

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

Thejas M Nair updated HIVE-6464:
--------------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

The two test failures are unrelated. See HIVE-6479 .

Patch committed to trunk. Thanks for the review [~navis]!


> 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)

Mime
View raw message