ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eduard Shangareev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-8911) While cache is restarting it's possible to start new cache with this name
Date Thu, 20 Dec 2018 22:10:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-8911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726256#comment-16726256
] 

Eduard Shangareev commented on IGNITE-8911:
-------------------------------------------

[~DmitriyGovorukhin], I don't think that statement in your first point is true.
As I see, GridStripedReadWriteLock contains collections of java ReadWriteLock and it is all.

> While cache is restarting it's possible to start new cache with this name
> -------------------------------------------------------------------------
>
>                 Key: IGNITE-8911
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8911
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Eduard Shangareev
>            Assignee: Eduard Shangareev
>            Priority: Major
>             Fix For: 2.8
>
>
> We have the state "restarting" for caches when we certainly now that these caches would
start at some moment in future. But we could start new cache with the same name.
> Plus, NPE is throwing when we try to get proxy for such caches (in "restarting" state).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message