[
https://issues.apache.org/jira/browse/IGNITE-8717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-8717:
-------------------------------------
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.
was:
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.
> Move persisted cache configuration to metastore
> -----------------------------------------------
>
> Key: IGNITE-8717
> URL: https://issues.apache.org/jira/browse/IGNITE-8717
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexey Goncharuk
> Priority: Major
>
> 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
(v7.6.3#76005)
