[
https://issues.apache.org/jira/browse/IGNITE-11541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16799022#comment-16799022
]
Alexey Goncharuk commented on IGNITE-11541:
-------------------------------------------
Suggested solution is to ignore static cache configuration for persistent
caches. At the same time I introduced an additional system property to keep the
old behavior. When this property is set, DDL operations over static persistent
caches are forbidden because it may lead to index corruption.
> Dynamic columns and indexes can be lost after the cluster restart
> -----------------------------------------------------------------
>
> Key: IGNITE-11541
> URL: https://issues.apache.org/jira/browse/IGNITE-11541
> Project: Ignite
> Issue Type: Bug
> Components: cache, persistence, sql
> Affects Versions: 2.7
> Reporter: Roman Guseinov
> Assignee: Alexey Goncharuk
> Priority: Critical
> Fix For: 2.8
>
> Attachments: StaticCacheAndDdlReproducer.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The case is the following:
> # Run a server node (persistence enabled. static cache configuration with
> queryEnities).
> # Add/drop column/index via DDL.
> # Restart the node with the same configuration.
> # The changes are lost...
> It seems the issue is related to merging cache metadata.
> There are some workarounds:
> # Remove/comment cache configuration. After the restart, the metadata will be
> loaded from the persistence store. This will work for a rolling restart.
> # Make the same changes in the configuration (update queryEntity). It
> requires the whole cluster restart.
> Reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
