[jira] [Updated] (UNOMI-572) Design issue with SchedulerService and conf reloading.

["Serge Huber (Jira)" <ji...@apache.org>]

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

Serge Huber updated UNOMI-572:
------------------------------
    Fix Version/s: unomi-3.0.0
                       (was: unomi-2.1.0)

> 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: unomi-2.0.0, unomi-1.6.0
>            Reporter: Kevan Jahanshahi
>            Priority: Major
>             Fix For: unomi-3.0.0
>
>
> 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.
> *Additional info: during the correction of this issue, please look for todos in unomi code that mention: UNOMI-572 they will probably need to be fixed at the same time.*



--
This message was sent by Atlassian Jira
(v8.20.10#820010)