ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Goncharuk (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-6629) Make service automatic redeployment configurable in ServiceConfiguration
Date Mon, 09 Apr 2018 13:05:00 GMT

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

Alexey Goncharuk updated IGNITE-6629:
-------------------------------------
    Fix Version/s:     (was: 2.5)
                   2.6

> 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
>            Assignee: Alexey Goncharuk
>            Priority: Major
>              Labels: Muted_test
>             Fix For: 2.6
>
>
> 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
(v7.6.3#76005)

Mime
View raw message