[IGNITE-8717] Move persisted cache configuration to metastore and introduce cache configuration versioning

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Maxim Muzafarov
• Reporter: Alexey Goncharuk
• Created: 06/Jun/18 08:53
• Updated: 22/Nov/21 07:41

Description

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.

Issue Links

• duplicates: IGNITE-7383 Failed to restore memory after cluster restart and activating from outdated node
• is related to: IGNITE-7788 Data loss after cold restart with PDS and cache group change
• is related to: IGNITE-9562 Destroyed cache that resurrected on an old offline node breaks PME
• relates to: IGNITE-7414 Cluster restart may lead to cluster activation error
• requires: IGNITE-10640 Create cluster-wide MetaStorage analogue
• links to: GitHub Pull Request #4837
• links to: GitHub Pull Request #5625
• links to: GitHub Pull Request #5625
• links to: MTCGA
• links to: Team City
• links to: upsource