You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by "Kevan Jahanshahi (Jira)" <ji...@apache.org> on 2022/05/23 08:49:00 UTC
[jira] [Updated] (UNOMI-572) Design issue with SchedulerService and conf reloading.
[ https://issues.apache.org/jira/browse/UNOMI-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevan Jahanshahi updated UNOMI-572:
-----------------------------------
Description:
The SchedulerService implementation is part of the *unomi-services* bundle, so in case somebody is editing a configuration file like this one:
{code:java}
org.apache.unomi.services {code}
The SchedulerService will be restarted, and some tasks/timers will be lost during the process, because not all tasks/timers are coming from the *unomi-services* bundle.
There is other bundles that would need to be notify about that restart to be able to re-register their tasks and timers.
Currently those tasks/timers coming from other bundles are lost, and this is causing major Unomi runtime instabilities.
For exemple: Recently we added a JSON Schema service that have a task to reload schemas from ES directly into RAM. This task is lost in case of conf editing on the mentioned conf, making JSON Schemas not reloaded anymore.
was:
The SchedulerService implementation is part of the *unomi-services* bundle, so in case somebody is editing a configuration file like this one:
{code:java}
org.apache.unomi.services {code}
The SchedulerService will be restarted, and some tasks/timers will be lost during the process, because not all tasks/timers are coming from the *unomi-services* bundle.
There is other bundles that would need to be notify about that restart to be able to re-register their tasks and timers.
Currently those tasks/timers coming from other bundles are lost, and this is causing major Unomi runtime instabilities.
> Design issue with SchedulerService and conf reloading.
> ------------------------------------------------------
>
> Key: UNOMI-572
> URL: https://issues.apache.org/jira/browse/UNOMI-572
> Project: Apache Unomi
> Issue Type: Bug
> Affects Versions: 2.0.0, 1.6.0
> Reporter: Kevan Jahanshahi
> Priority: Major
>
> The SchedulerService implementation is part of the *unomi-services* bundle, so in case somebody is editing a configuration file like this one:
> {code:java}
> org.apache.unomi.services {code}
> The SchedulerService will be restarted, and some tasks/timers will be lost during the process, because not all tasks/timers are coming from the *unomi-services* bundle.
> There is other bundles that would need to be notify about that restart to be able to re-register their tasks and timers.
> Currently those tasks/timers coming from other bundles are lost, and this is causing major Unomi runtime instabilities.
> For exemple: Recently we added a JSON Schema service that have a task to reload schemas from ES directly into RAM. This task is lost in case of conf editing on the mentioned conf, making JSON Schemas not reloaded anymore.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)