You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Aleksey Plekhanov (Jira)" <ji...@apache.org> on 2020/06/26 15:00:00 UTC

[jira] [Updated] (IGNITE-6629) Make service automatic redeployment configurable in ServiceConfiguration

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

Aleksey Plekhanov updated IGNITE-6629:
--------------------------------------
    Fix Version/s:     (was: 2.9)
                   2.10

> Make service automatic redeployment configurable in ServiceConfiguration
> ------------------------------------------------------------------------
>
>                 Key: IGNITE-6629
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6629
>             Project: Ignite
>          Issue Type: Improvement
>          Components: managed services
>    Affects Versions: 2.3
>            Reporter: Ivan Rakov
>            Priority: Major
>              Labels: Muted_test
>             Fix For: 2.10
>
>
> Before 2.3, if persistence was enabled globally, services were recovered along with system cache. But in 2.3, persistence can be enabled for per data region (IGNITE-6030), and system data region is not persistent.
> We should add feaure to configure service redeployment after restart. Service-related information should be stored in Metastore instead of system cache.
> IgniteChangeGlobalStateServiceTest#testDeployService should be fixed under this ticket.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)