[
https://issues.apache.org/jira/browse/IGNITE-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996349#comment-15996349
]
ASF GitHub Bot commented on IGNITE-1094:
----------------------------------------
GitHub user voipp opened a pull request:
https://github.com/apache/ignite/pull/1904
IGNITE-1094 corrupted cache recovery resolved
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/voipp/ignite Ignite-1094
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1904.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 #1904
----
commit e47ce114e6431cc55e58ea2fdcbdc53b93ea57df
Author: voipp <[email protected]>
Date: 2017-05-03T13:22:19Z
IGNITE-1094 corrupted cache recovery resolved
----
> Ignite.createCache(CacheConfiguration) hangs if some exception occurs during
> cache initialization
> -------------------------------------------------------------------------------------------------
>
> Key: IGNITE-1094
> URL: https://issues.apache.org/jira/browse/IGNITE-1094
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Reporter: Sergey Evdokimov
> Assignee: Alexey Kuznetsov
> Labels: Muted_test
> Fix For: 2.1
>
>
> User can pass broken configuration, for example, store factory that throws
> exception from create() method. I created test to demonstrate the problem.
> See IgniteDynamicCacheStartSelfTest#testBrokenStoreFactory in 'ignite-1094'
> branch
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
