You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/01 16:44:00 UTC

[jira] [Commented] (IGNITE-8717) Move persisted cache configuration to metastore and introduce cache configuration versioning

    [ https://issues.apache.org/jira/browse/IGNITE-8717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16942132#comment-16942132 ] 

Maxim Muzafarov commented on IGNITE-8717:
-----------------------------------------

[~antonovsergey93], [~agoncharuk] 

Are we expecting this issue in 2.8?

> Move persisted cache configuration to metastore and introduce cache configuration versioning
> --------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-8717
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8717
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Alexey Goncharuk
>            Assignee: Sergey Antonov
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently, we persist cache configuration to local files which resulted in several inconsistencies when a node misses configuration update (create index, cache destroy, etc).
> I think the cache configuration should be saved to the metastore the same way as baseline topology is saved. Same mechanics should be used for conflicting configuration updates resolution.
> Along with cache configuration, it also makes sense to move marshaller and binary metadata to the metastore.



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