[
https://issues.apache.org/jira/browse/QUARKS-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224910#comment-15224910
]
Victor Dogaru commented on QUARKS-105:
--------------------------------------
Rough Quarks.MonitorApp algorithm for job restarts:
{noformat}
if (received jobEvent.health == UNHEALTHY) {
config = JobRegistry.getConfiguration(jobId);
config.decrementRestartCount()
if (config.restartCount > 0) {
topology = AppRegistry.getTopology(job.name);
JobRegistry.remove(jobId);
AppRegistryControl.submit(topology, config);
}
}
{noformat}
This needs the following functionality:
1. The runtime adds submission configuration to the JobRegistry when a job is
submitted
2. Topologies registered with ApplicationService are uniquely identified by
applicationName. The current AppService implementation requires the application
names be unique. Should the ApplicationService document this?
> Configurable number of application restarts
> -------------------------------------------
>
> Key: QUARKS-105
> URL: https://issues.apache.org/jira/browse/QUARKS-105
> Project: Quarks
> Issue Type: Sub-task
> Components: Applications, Runtime
> Reporter: Victor Dogaru
> Labels: failure-recovery
>
> This configuration would allow a developer to specify the number of times the
> system should attempt to restart an application which had terminated because
> of an unhandled exception.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
