[
https://issues.apache.org/jira/browse/HIVE-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13270114#comment-13270114
]
Hudson commented on HIVE-3000:
------------------------------
Integrated in Hive-trunk-h0.21 #1417 (See
[https://builds.apache.org/job/Hive-trunk-h0.21/1417/])
HIVE-3000 Potential infinite loop / log spew in ZookeeperHiveLockManager
(njain via kevinwilfong) (Revision 1335106)
Result = FAILURE
kevinwilfong :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1335106
Files :
*
/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/lockmgr/zookeeper/ZooKeeperHiveLockManager.java
> Potential infinite loop / log spew in ZookeeperHiveLockManager
> --------------------------------------------------------------
>
> Key: HIVE-3000
> URL: https://issues.apache.org/jira/browse/HIVE-3000
> Project: Hive
> Issue Type: Bug
> Components: Locking
> Affects Versions: 0.9.0
> Reporter: Paul Yang
> Assignee: Namit Jain
> Fix For: 0.10.0
>
> Attachments: HIVE-3000.D3063.1.patch
>
>
> See ZookeeperHiveLockManger.lock()
> If Zookeeper is in a bad state, it's possible to get an exception (e.g.
> org.apache.zookeeper.KeeperException$SessionExpiredException) when we call
> lockPrimitive(). There is a bug in the exception handler where the loop does
> not exit because the break in the switch statement gets out the switch, not
> the do..while loop. Because tryNum was not incremented due to the exception,
> lockPrimitive() will be called in an infinite loop, as fast as possible.
> Since the exception is printed for each call, Hive will produce significant
> log spew.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
