You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Semyon Danilov (Jira)" <ji...@apache.org> on 2022/05/18 07:19:00 UTC
[jira] [Updated] (IGNITE-16986) Incorrect GridCacheProcessor#stop parameters
[ https://issues.apache.org/jira/browse/IGNITE-16986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Semyon Danilov updated IGNITE-16986:
------------------------------------
Description: IGNITE-8911 introduced an optimization that lets ignite skip cache destroy if the whole cache group is going to be destroyed. However, this leads to GridCacheManager#stop receiving incorrect destroy argument and potentially not performing some tasks (for example, not dropping statistics).
> Incorrect GridCacheProcessor#stop parameters
> ---------------------------------------------
>
> Key: IGNITE-16986
> URL: https://issues.apache.org/jira/browse/IGNITE-16986
> Project: Ignite
> Issue Type: Bug
> Reporter: Semyon Danilov
> Assignee: Semyon Danilov
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> IGNITE-8911 introduced an optimization that lets ignite skip cache destroy if the whole cache group is going to be destroyed. However, this leads to GridCacheManager#stop receiving incorrect destroy argument and potentially not performing some tasks (for example, not dropping statistics).
--
This message was sent by Atlassian Jira
(v8.20.7#820007)