[
https://issues.apache.org/jira/browse/IGNITE-8717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16661869#comment-16661869
]
Ignite TC Bot commented on IGNITE-8717:
---------------------------------------
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Activate | Deactivate Cluster{color} [[tests 0 TIMEOUT , Exit
Code |https://ci.ignite.apache.org/viewLog.html?buildId=2149077]]
* IgniteClusterActivateDeactivateTest.testConcurrentJoinAndActivate (last
started)
{panel}
[TeamCity Run
All|http://ci.ignite.apache.org/viewLog.html?buildId=2149179&buildTypeId=IgniteTests24Java8_RunAll]
> 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
> Assignee: Sergey Antonov
> 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)
