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

Posted to dev@oozie.apache.org by "Rohini Palaniswamy (JIRA)" <ji...@apache.org> on 2013/03/07 00:34:13 UTC

[jira] [Updated] (OOZIE-1255) latest/future check for hcat can cause shutdown to hang

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

Rohini Palaniswamy updated OOZIE-1255:
--------------------------------------

    Attachment: OOZIE-1255-1.patch

Have not added a test as it is not that easy to add a reliable one as the hdfs check goes through really fast. Tested manually.
                
> latest/future check for hcat can cause shutdown to hang
> -------------------------------------------------------
>
>                 Key: OOZIE-1255
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1255
>             Project: Oozie
>          Issue Type: Sub-task
>            Reporter: Rohini Palaniswamy
>            Assignee: Rohini Palaniswamy
>             Fix For: trunk, 4.0.0
>
>         Attachments: OOZIE-1255-1.patch
>
>
>   For the testcase, having a coordinator with 1 min frequency and start time 1 month back, to determine latest(0) around 43K hcat calls were made (table was empty with no partitions). When trying to shutdown it took a really long time 5-10 mins. 
> Rogue jobs like this can cause problems. Need to check for Thread interrupted status and break out of the loop.

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