[
https://issues.apache.org/jira/browse/IGNITE-12614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Steshin updated IGNITE-12614:
--------------------------------------
Description:
Currently, anyone is able to deactivate cluster with command line utility
(control.sh). Probably with JMX too. That would lead to data loss when the
persistence is off. In-memory data is erased during deactivation. Such behavior
can be considered as unexpected to user.
Suggestions:
1) Disallow silent deactivation of cluster keeping caches. Show a warning
like “Your cluster has in-memory cache configured. During deactivation all data
from these caches will be cleared!”
2) Add param ‘--force’ which skips the warning message.
was:
Currently, anyone is able to deactivate cluster with command line utility
(control.sh). Probably with JMX too. That would lead to data loss when the
persistence is off. In-memory data is erased during deactivation. Such behavior
can be considered as unexpected to user.
Suggestions:
1) Disallow silent deactivate cluster keeping caches. Show a warning like
“Your cluster has in-memory cache configured. During deactivation all data from
these caches will be cleared!”
2) Add param ‘--force’ which skips the warning message.
> Disallow silent deactivation of cluster to prevent in-mem data loss.
> --------------------------------------------------------------------
>
> Key: IGNITE-12614
> URL: https://issues.apache.org/jira/browse/IGNITE-12614
> Project: Ignite
> Issue Type: Bug
> Reporter: Vladimir Steshin
> Priority: Major
>
> Currently, anyone is able to deactivate cluster with command line utility
> (control.sh). Probably with JMX too. That would lead to data loss when the
> persistence is off. In-memory data is erased during deactivation. Such
> behavior can be considered as unexpected to user.
> Suggestions:
> 1) Disallow silent deactivation of cluster keeping caches. Show a warning
> like “Your cluster has in-memory cache configured. During deactivation all
> data from these caches will be cleared!”
> 2) Add param ‘--force’ which skips the warning message.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
