You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jim Challenger (JIRA)" <de...@uima.apache.org> on 2015/03/06 18:13:38 UTC

[jira] [Resolved] (UIMA-3703) DUCC Add uuid to NodeIdentity

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

Jim Challenger resolved UIMA-3703.
----------------------------------
    Resolution: Won't Fix

The actual need for this is no longer clear.  Will reopen in future if needed.

> DUCC Add uuid to NodeIdentity
> -----------------------------
>
>                 Key: UIMA-3703
>                 URL: https://issues.apache.org/jira/browse/UIMA-3703
>             Project: UIMA
>          Issue Type: Improvement
>          Components: DUCC
>    Affects Versions: 1.0.0-Ducc
>            Reporter: Jim Challenger
>            Assignee: Jim Challenger
>            Priority: Minor
>             Fix For: future-DUCC
>
>
> The NodeIdentity should generate a UUID and make it available to interested parties.  The UUID is to be used by RM and WS and maybe others to detect duplicate Agent instances on the same node, the presence of which can cause all sorts of problems including permanently "hung" jobs.
> The proposed use of this is for RM to 'blacklist' the duplicate Agents, purging all work from them, and refuse to allocate new work on them until they are cleaned up and whitelisted again.  WS would reveal the problem so admins could  be aware and clean up.
> Logic to use this will be implemented later under separate JIRAs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)