[
https://issues.apache.org/jira/browse/IGNITE-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16094386#comment-16094386
]
Alexey Kuznetsov commented on IGNITE-1094:
------------------------------------------
[~yzhdanov] There are 5 tests , do you find them sufficient ?
Tests on 2 server nodes:
||Test scenario||Expected result||
|Node 0 initiates cache creation. Both nodes try to create it, but both fail.
|Exception thrown only on Node 0, cache is reverted.|
|Node 0 initiates cache creation. Both nodes try to create it, but Node 1
fails. |Exception thrown only on Node 0, cache is reverted.|
|Node 0 initiates corrupted and normal cache. Both nodes try to create them,
but both fail to create corrupted cache. |Exception thrown only on Node 0, both
caches are reverted.|
|Node 0 initiates corrupted and normal cache. Both nodes try to create them,
but Node 1 fail to create corrupted cache. |Exception thrown only on Node 0,
both caches are reverted.|
|Node 0 initiates 2 corrupted caches. Both nodes try to create them, but Node 1
fails. |Exception thrown only on Node 0, both caches are reverted.|
> 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.2
>
>
> 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.4.14#64029)
