ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anton Vinogradov <avinogra...@gridgain.com>
Subject Re: IgniteDataStreamer silently fails on a server node
Date Wed, 21 Feb 2018 12:49:58 GMT
Nikolay,

I checked your reproducer and it looks like retry helps data streamer to
solve this.
I
set org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl#DFLT_MAX_REMAP_CNT
to zero and see test fails now.

Looks like second attempt is successful for such case.

On Wed, Feb 21, 2018 at 1:36 PM, Dmitriy Setrakyan <dsetrakyan@apache.org>
wrote:

> On Wed, Feb 21, 2018 at 12:10 AM, Nikolay Izhikov <nizhikov@apache.org>
> wrote:
>
> > Hello, Igniters.
> >
> > > Does this exception happen because IgniteUuid class is not correctly
> > > handled?
> >
> > Yes. I've fixed it.
> > But story doesn't end :)
> >
> > > As far as propagating exceptions, addData(...) is asynchronous
> operation
> > > and returns IgniteFuture.
> >
> > Thank you, my bad.
> >
> > But, I can't understand when returned future should complete?
> >
> > Javadocs or documentation doesn't explain it.
> > Also, I can't find any tests that checks future returned from addData.
> >
> > Can someone explan it to me?
> >
>
> The returned future should complete either when the data is successfully
> stored in cache, or whenever the failure occurs.
>

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