[jira] [Resolved] (UIMA-4638) DUCC Orchestrator (OR) should not use "dead reckoning" to determine if Reservation is for JDs

["Lou DeGenaro (JIRA)" <de...@uima.apache.org>]

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

Lou DeGenaro resolved UIMA-4638.
--------------------------------
    Resolution: Fixed

OR will set flag in Reservation to indicate JD use upon creation and will check same on restart.

> DUCC Orchestrator (OR) should not use "dead reckoning" to determine if Reservation is for JDs
> ---------------------------------------------------------------------------------------------
>
>                 Key: UIMA-4638
>                 URL: https://issues.apache.org/jira/browse/UIMA-4638
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>             Fix For: 2.1.0-Ducc
>
>
> When OR boots, previous JD Reservation(s) should be cancelled for cold+warm starts.
> OR uses current ducc.properties defined ducc.jd.host.class to determine if any previously existing JD Reservation(s) should be cancelled.  If the class is unchanged, then the cancellation is issued as expected.  But if the class is changed the OR will erroneously fail to cancel.



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