You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Mona Chitnis (JIRA)" <ji...@apache.org> on 2013/06/17 19:15:21 UTC
[jira] [Reopened] (OOZIE-1418) Fix bugs around ActionKillX not
setting end time, V2SLAServlet and exception handling for event threads
[ https://issues.apache.org/jira/browse/OOZIE-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mona Chitnis reopened OOZIE-1418:
---------------------------------
Point #3 from description not resolved. Reopening jira and will commit incremental patch
> Fix bugs around ActionKillX not setting end time, V2SLAServlet and exception handling for event threads
> -------------------------------------------------------------------------------------------------------
>
> Key: OOZIE-1418
> URL: https://issues.apache.org/jira/browse/OOZIE-1418
> Project: Oozie
> Issue Type: Bug
> Affects Versions: trunk
> Reporter: Mona Chitnis
> Assignee: Mona Chitnis
> Fix For: trunk
>
> Attachments: OOZIE-1418.patch
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Bug fixes for the following:
> 1. When a workflow action is killed via ActionKillXCommand, the end time of the action is not set. You can see it even now for KILLED actions on the web-console. This is leading to NPE in Sla calculation
> 2. V2SLAServlet constructor had wrong argument - failing AuthFilter init()
> 3. Handle case on Coordinator rerun, where sla job is rerun with a different conf without sla, thus having no SLA registration record to update
> 4. Exception handling for worker threads spawned from EventHandlerService and SLAService, to avoid thread from dying and quitting processing any events in its queue.
--
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