hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (HIVE-3000) Potential infinite loop / log spew in ZookeeperHiveLockManager
Date Mon, 07 May 2012 16:44:50 GMT

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

Ashutosh Chauhan reassigned HIVE-3000:
--------------------------------------

    Assignee: Namit Jain
    
> 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

        

Mime
View raw message