[
https://issues.apache.org/jira/browse/IGNITE-16579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-16579:
-------------------------------------
Ignite Flags: Release Notes Required
> Cluster deactivation can get stuck
> ----------------------------------
>
> Key: IGNITE-16579
> URL: https://issues.apache.org/jira/browse/IGNITE-16579
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.12
> Reporter: Vyacheslav Koptilin
> Assignee: Vyacheslav Koptilin
> Priority: Blocker
> Fix For: 2.13
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Cluster deactivation that is executed via Java API or control utility without
> --force flag can get stuck in the case when the cluster contains persistent
> caches and client nodes that do not provide DataStorageConfiguration. In that
> case, client nodes can erroneously consider that all caches are in-memory and
> therefore will not start the corresponding exchange process at all, unlike
> server nodes.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
