You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org> on 2013/08/06 19:08:48 UTC

[jira] [Created] (UIMA-3153) Ducc Agent should start collecting rogue processes only after it receives initial Ducc state update

Jerry Cwiklik created UIMA-3153:
-----------------------------------

             Summary: Ducc Agent should start collecting rogue processes only after it receives initial Ducc state update
                 Key: UIMA-3153
                 URL: https://issues.apache.org/jira/browse/UIMA-3153
             Project: UIMA
          Issue Type: Bug
          Components: DUCC
            Reporter: Jerry Cwiklik
            Assignee: Jerry Cwiklik
             Fix For: 1.0-Ducc


Agent starts collecting rogue processes immediately after launch and possibly before receiving Ducc state update. This may lead to a problem of falsely identifying a rogue process belonging to a user with existing reservation. On agent/system bounce, such processes are marked as rogues and subsequently killed. Modify agent to begin collecting user processes and detecting rogues only after a ducc state update is processed. When the state update arrives, the agent receives all reservations and will have necessarily information to detect true rogues on a node.

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