You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2013/01/09 11:28:49 UTC
[jira] [Commented] (HIVE-3659)
TestHiveHistory::testQueryloglocParentDirNotExist Test fails on Windows
because of some resource leaks in ZK
[ https://issues.apache.org/jira/browse/HIVE-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13548114#comment-13548114 ]
Hudson commented on HIVE-3659:
------------------------------
Integrated in Hive-trunk-hadoop2 #54 (See [https://builds.apache.org/job/Hive-trunk-hadoop2/54/])
HIVE-3659 : TestHiveHistory::testQueryloglocParentDirNotExist Test fails on Windows because of some resource leaks in ZK (Kanna Karanam via Ashutosh Chauhan) (Revision 1407719)
Result = ABORTED
hashutosh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1407719
Files :
* /hive/trunk/ql/src/test/org/apache/hadoop/hive/ql/history/TestHiveHistory.java
> TestHiveHistory::testQueryloglocParentDirNotExist Test fails on Windows because of some resource leaks in ZK
> ------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-3659
> URL: https://issues.apache.org/jira/browse/HIVE-3659
> Project: Hive
> Issue Type: Bug
> Components: Tests
> Affects Versions: 0.10.0, 0.9.1
> Reporter: Kanna Karanam
> Assignee: Kanna Karanam
> Labels: Windows
> Fix For: 0.10.0
>
> Attachments: HIVE-3659.1.patch.txt
>
>
> Hive uses ZK for locking. In some test cases, ZK is not behaving well. In thread dumps, I saw it is waiting for locks to be released but they were not getting released. Hive tries to release locks but keeps failing, it eventually times out for its release attempts, which in default settings takes 10 mins. This is also the cause of why some queries take extra-ordinarily long to run. I suggest to disable ZK locking till ZK is certified for windows.
> In this test case, I don’t see a requirement to use ZK so I am disabling the HiveConf.ConfVars.HIVE_SUPPORT_CONCURRENCY to work around the issue.
--
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