[
https://issues.apache.org/jira/browse/IGNITE-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15893906#comment-15893906
]
Yakov Zhdanov commented on IGNITE-1094:
---------------------------------------
Alexey, implementation is incorrect. I have to cancel this patch.
This should be fixed in the following way (at least it seems so to me)
1. all nodes try to init cache locally
2. if error occurs on any node then exchange coordinator should be notified.
3. coordinator should send
{{org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsFullMessage}}
message containing error flag to all cache nodes
4. all cache nodes should revert the changes
5. exception should be thrown on initiator node (who called create cache)
Please make sure to add multi-node tests with conditional exception throwing
from factories (only on 1 node from several nodes topology).
Thanks!
> 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)
