ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vladimir Ozerov <voze...@gridgain.com>
Subject Re: Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization Ignite-1049
Date Fri, 28 Apr 2017 13:41:21 GMT
Aleksey,
I am thinking on whether we should do this during exchange step or not. In
principle, validation is rather fast operation, so we can do it inside
discovery thread even before descriptor is created and registered.

Alex G., Semen,
What do you think?

On Fri, Apr 28, 2017 at 12:36 PM, ALEKSEY KUZNETSOV <
alkuznetsov.sb@gmail.com> wrote:

> Hi, Igntrs!
> https://issues.apache.org/jira/browse/IGNITE-1094
>
> I've come up with solution. Put exception into
> GridDhtPartitionsSingleMessage indicating cache creation failed on local
> node. Send it to coordinator.
> Coordinator's GridCachePartitionExchangeManager while processing would
> extract exchangeId from message and find GridDhtPartitionsExchangeFuture
> with the same exchangeId.
>
>
> Exactly this exchange future must contain DynamicCacheChangeRequest with
> cache , causing exception.
> Then the cache descriptor could be removed.
>
>
> But im concerning about exchangeId uniqueness.
>
> --
>
> *Best Regards,*
>
> *Kuznetsov Aleksey*
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message