[
https://issues.apache.org/jira/browse/IGNITE-8911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726330#comment-16726330
]
ASF GitHub Bot commented on IGNITE-8911:
----------------------------------------
GitHub user EdShangGG opened a pull request:
https://github.com/apache/ignite/pull/5717
IGNITE-8911
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8911-2
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5717.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5717
----
commit ec1b9175835e5ab8f34a96af3b7df88d67850def
Author: Eduard Shangareev <eshangareev@...>
Date: 2018-12-11T09:30:06Z
IGNITE-8911
commit af426af1195bb9076a41f0025abc3976ebba2e9c
Author: Eduard Shangareev <eshangareev@...>
Date: 2018-12-20T23:39:44Z
IGNITE-8911
----
> 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)
