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

Alexey Kuznetsov commented on IGNITE-1094:
------------------------------------------

Tests were added, you can see them above in table. 
Algorithm , proposed by [~yzhdanov] was partially implemented. The problems I 
faced during implementation is as follows,
when exception got thrown , newly created cache group frozens awaiting for 
partition ready function to finish.

Pull request to old branch, containing first test for this ticket by 
[~sevdokimov-gg] 
([commit|https://github.com/apache/ignite/commit/658431e912da008bee737e7c6f21d80502cddc34])
[pull request|https://github.com/apache/ignite/pull/2332]

My commit(in pull request) u can see here : 
https://github.com/apache/ignite/pull/2332/commits/e5f0c8915fda183fe74bb3b59d4304e1021b5a52

> 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)

Reply via email to