You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Burn Lewis (JIRA)" <de...@uima.apache.org> on 2017/03/23 13:32:41 UTC

[jira] [Commented] (UIMA-5246) Serialize re-registration of DUCC services to reduce chance of duplicate services

    [ https://issues.apache.org/jira/browse/UIMA-5246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938298#comment-15938298 ] 

Burn Lewis commented on UIMA-5246:
----------------------------------

One bug that caused duplicate services has been fixed in 5372.  Marking the DB entry as archived could be done earlier ... perhaps the unregister should fail quickly if the DB cannot be updated.

> Serialize re-registration of DUCC services to reduce chance  of duplicate services
> ----------------------------------------------------------------------------------
>
>                 Key: UIMA-5246
>                 URL: https://issues.apache.org/jira/browse/UIMA-5246
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Burn Lewis
>            Assignee: Burn Lewis
>             Fix For: future-DUCC
>
>
> After an unregister + register ducc-mon has sometimes shown 2 service with the same endpoint.  Apparently the older unregistered one was not marked as "archived" in the DB.  Currently new instances of the service may be created before all of the old ones have been removed - would be better if the old service is completely removed before the new instances created.
> Should also handle failures to update the DB.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)