[jira] [Commented] (UIMA-5060) DUCC Orchestrator (OR) "warm" restart issues
[ https://issues.apache.org/jira/browse/UIMA-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15589568#comment-15589568 ] Lou DeGenaro commented on UIMA-5060: - remove sequenceNumberStateAbbreviated from orchestrator-state.json, since it is obsolete > DUCC Orchestrator (OR) "warm" restart issues > > > Key: UIMA-5060 > URL: https://issues.apache.org/jira/browse/UIMA-5060 > Project: UIMA > Issue Type: Bug > Components: DUCC >Affects Versions: 2.2.0-Ducc >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro > Fix For: 2.2.0-Ducc > > > Address issues pertaining to the ability to shutdown and restart the OR > component without loss of active jobs or services or AP's (aka Managed > Reservations). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (UIMA-5060) DUCC Orchestrator (OR) "warm" restart issues
[ https://issues.apache.org/jira/browse/UIMA-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588800#comment-15588800 ] Lou DeGenaro commented on UIMA-5060: - for restoration of next service sequence number, use the greater of seqno in state/sm.properties and historical data from database comprising services. - log a WARNing in sm.log if historical data is used. > DUCC Orchestrator (OR) "warm" restart issues > > > Key: UIMA-5060 > URL: https://issues.apache.org/jira/browse/UIMA-5060 > Project: UIMA > Issue Type: Bug > Components: DUCC >Affects Versions: 2.2.0-Ducc >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro > Fix For: 2.2.0-Ducc > > > Address issues pertaining to the ability to shutdown and restart the OR > component without loss of active jobs or services or AP's (aka Managed > Reservations). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (UIMA-5060) DUCC Orchestrator (OR) "warm" restart issues
[ https://issues.apache.org/jira/browse/UIMA-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15586659#comment-15586659 ] Lou DeGenaro commented on UIMA-5060: - add to DUCC Book a chapter in the Admin Guide about the state directory, describing the sub-directories and files therein > DUCC Orchestrator (OR) "warm" restart issues > > > Key: UIMA-5060 > URL: https://issues.apache.org/jira/browse/UIMA-5060 > Project: UIMA > Issue Type: Bug > Components: DUCC >Affects Versions: 2.2.0-Ducc >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro > Fix For: 2.2.0-Ducc > > > Address issues pertaining to the ability to shutdown and restart the OR > component without loss of active jobs or services or AP's (aka Managed > Reservations). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (UIMA-5060) DUCC Orchestrator (OR) "warm" restart issues
[ https://issues.apache.org/jira/browse/UIMA-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15585621#comment-15585621 ] Lou DeGenaro commented on UIMA-5060: - for restoration of next job/reservation sequence number, use the greater of seqno in state/orchestrator.properties and historical data from database comprising jobs and reservations. - log a WARNing in or.log if historical data is used. > DUCC Orchestrator (OR) "warm" restart issues > > > Key: UIMA-5060 > URL: https://issues.apache.org/jira/browse/UIMA-5060 > Project: UIMA > Issue Type: Bug > Components: DUCC >Affects Versions: 2.2.0-Ducc >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro > Fix For: 2.2.0-Ducc > > > Address issues pertaining to the ability to shutdown and restart the OR > component without loss of active jobs or services or AP's (aka Managed > Reservations). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (UIMA-5060) DUCC Orchestrator (OR) "warm" restart issues
[ https://issues.apache.org/jira/browse/UIMA-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15583126#comment-15583126 ] Lou DeGenaro commented on UIMA-5060: - reduce OR dependencies on CommonConfiguration - employ DuccPropertiesResolver > DUCC Orchestrator (OR) "warm" restart issues > > > Key: UIMA-5060 > URL: https://issues.apache.org/jira/browse/UIMA-5060 > Project: UIMA > Issue Type: Bug > Components: DUCC >Affects Versions: 2.2.0-Ducc >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro > Fix For: 2.2.0-Ducc > > > Address issues pertaining to the ability to shutdown and restart the OR > component without loss of active jobs or services or AP's (aka Managed > Reservations). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (UIMA-5060) DUCC Orchestrator (OR) "warm" restart issues
[ https://issues.apache.org/jira/browse/UIMA-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576229#comment-15576229 ] Lou DeGenaro commented on UIMA-5060: - Fix leak of JD entries in OR's map of processId-to-jobId. - Make ProcessToJobMap its own class and insure code that employs same does not use stale copy. - Code refactoring for simplification and clarity in ProcessAccounting. > DUCC Orchestrator (OR) "warm" restart issues > > > Key: UIMA-5060 > URL: https://issues.apache.org/jira/browse/UIMA-5060 > Project: UIMA > Issue Type: Bug > Components: DUCC >Affects Versions: 2.2.0-Ducc >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro > Fix For: 2.2.0-Ducc > > > Address issues pertaining to the ability to shutdown and restart the OR > component without loss of active jobs or services or AP's (aka Managed > Reservations). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (UIMA-5060) DUCC Orchestrator (OR) "warm" restart issues
[
https://issues.apache.org/jira/browse/UIMA-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15473897#comment-15473897
]
Lou DeGenaro commented on UIMA-5060:
Enhance stop_ducc and, for symmetry, start_ducc to support option -c head,
where head represents { or, rm, pm, sm, ws, db, broker }. That is, all
top-level DUCC daemons except agents.
> DUCC Orchestrator (OR) "warm" restart issues
>
>
> Key: UIMA-5060
> URL: https://issues.apache.org/jira/browse/UIMA-5060
> Project: UIMA
> Issue Type: Bug
> Components: DUCC
>Affects Versions: 2.2.0-Ducc
>Reporter: Lou DeGenaro
>Assignee: Lou DeGenaro
>
> Address issues pertaining to the ability to shutdown and restart the OR
> component without loss of active jobs or services or AP's (aka Managed
> Reservations).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (UIMA-5060) DUCC Orchestrator (OR) "warm" restart issues
[ https://issues.apache.org/jira/browse/UIMA-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467634#comment-15467634 ] Lou DeGenaro commented on UIMA-5060: Previously OR supported --cold and --warm starts, where the former caused all active work to be moved to the Completed state (no recovery) and the latter caused partial recovery (active Jobs forced to Completed, while active Reservations recovered). We abandon introducing a third --hot option that would implement a full recovery and instead re-purpose --warm to do so. Partial recovery is deemed unnecessary and somewhat arbitrary. > DUCC Orchestrator (OR) "warm" restart issues > > > Key: UIMA-5060 > URL: https://issues.apache.org/jira/browse/UIMA-5060 > Project: UIMA > Issue Type: Bug > Components: DUCC >Affects Versions: 2.2.0-Ducc >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro > > Address issues pertaining to the ability to shutdown and restart the OR > component without loss of active jobs or services or AP's (aka Managed > Reservations). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
