You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Lou DeGenaro (JIRA)" <de...@uima.apache.org> on 2013/02/15 19:15:13 UTC

[jira] [Assigned] (UIMA-2641) DUCC orchestrator (OR) should mark unused, stubbornly alive Job Processes (JPs) as "Stopped" when all work items are accounted for...

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

Lou DeGenaro reassigned UIMA-2641:
----------------------------------

    Assignee: Lou DeGenaro
    
> DUCC orchestrator (OR) should mark unused, stubbornly alive Job Processes (JPs) as "Stopped" when all work items are accounted for...
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: UIMA-2641
>                 URL: https://issues.apache.org/jira/browse/UIMA-2641
>             Project: UIMA
>          Issue Type: Improvement
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>            Priority: Minor
>
> Recently, a job was submitted but got stuck in state "Completing".  All work items had completed.  During the run a Job Process (JP) was launched and got stuck in Initializing state because the machine on which it (once) existed crashed and (therefore) the DUCC Agent responsible was unable to report or take action.  This stuck JP was keeping the job from advancing to the "Completed" state.
> The user issued the DUCC cancel command using flag --dpid to cancel the bogus JP and the job completed normally.
> This situation could be detected by the orchestrator (OR) and handled w/o human (user) intervention.

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