You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Kuznetsov (JIRA)" <ji...@apache.org> on 2017/07/12 09:26:00 UTC

[jira] [Commented] (IGNITE-1094) Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization

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

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

[~yzhdanov] Should we implement ticket as you on 3 march of 2017 ?
I have one more question : should node, that caught exception, revert cache prior to sending partition single message with that exception ? Or it should revert changes after gettinh full message ?

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