[ https://issues.apache.org/jira/browse/IGNITE-8911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590134#comment-16590134 ]
ASF GitHub Bot commented on IGNITE-8911: ---------------------------------------- GitHub user EdShangGG opened a pull request: https://github.com/apache/ignite/pull/4605 IGNITE-8911 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8911-1 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4605.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 #4605 ---- commit b22bbf79dbcfb5127b41cde9d955542f1e1bb033 Author: EdShangGG <eshangareev@...> Date: 2018-07-31T14:03:55Z IGNITE-8911 While cache is restarting it's possible to start new cache with this name commit 55bb3ac8cf334ddf84877e8c907ee2900258b12e Author: EdShangGG <eshangareev@...> Date: 2018-07-31T15:50:28Z IGNITE-8911 While cache is restarting it's possible to start new cache with this name -added test commit 30333bf4a7a58d0b18e2f425ea6a645611c48f3a Author: EdShangGG <eshangareev@...> Date: 2018-08-23T12:04:03Z Merge branch 'master1' into ignite-8911-1 ---- > 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 > > 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)