[
https://issues.apache.org/jira/browse/EDGENT-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale LaBossiere reassigned EDGENT-397:
--------------------------------------
Assignee: (was: Dale LaBossiere)
> Support failed-job-restart in IotProvider
> -----------------------------------------
>
> Key: EDGENT-397
> URL: https://issues.apache.org/jira/browse/EDGENT-397
> Project: Edgent
> Issue Type: New Feature
> Components: Providers
> Reporter: Dale LaBossiere
>
> IotProvider includes the JobMonitorApp. JobMonitorApp requires that a
> JobRegistryService is registered in order to receive job status events to
> detect failed jobs so that it can restart them.
> Neither IotProvider nor anything it uses is registering a JobRegistryService
> so jobs aren't restarted when using the IotProvider.
> Since IotProvider doesn't document that it adds JobMonitorApp and it doesn't
> state that it provides failed app restart capability, I've decided this is
> really a feature request. The original non-restarting behavior must be
> preserved as the default behavior.
> Might want to get a better understanding of failure handling before exposing
> job-restart via IotProvider - see EDGENT-382.
> See also EDGENT-396 and EDGENT-112
> Note, JobMonitorAppTest verifies the app in isolation however there isn't an
> analogous test in an IotProvider context. IotProviderTest should be enhanced
> accordingly. With a couple of tweaks it can leverage some of
> JobMonitorAppTest.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
