[
https://issues.apache.org/jira/browse/IGNITE-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928205#comment-15928205
]
Alexey Kuznetsov edited comment on IGNITE-1094 at 3/17/17 8:05 AM:
-------------------------------------------------------------------
[~yzhdanov] As l understand, when we create cache by calling
_ignite(0).createCache(...)_ the message with cache config is broadcasted to
all nodes at first, and only then the cache got created().
So, perhaps, we can throw exception on initiator node and ignore exception on
other nodes.
Why do we need to notify coordinator?
And what changes we should revert at nodes ?
was (Author: alexey kuznetsov):
[~yzhdanov] As l understand, when we create cache by calling
_ignite(0).createCache(...)_ the message with cache config is broadcasted to
all nodes at first, and only then the cache got created().
So, perhaps, we can firstly try create cache and if succeeded , broadcast it to
everybody.
> 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.0
>
>
> 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)
