Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CA+0=VoXUVmJK32Mckqccv-PG2F6Qd=0GfYZJUy2piHrAXs8iUA@mail.gmail.com>
References: 
 <CA+0=VoXUVmJK32Mckqccv-PG2F6Qd=0GfYZJUy2piHrAXs8iUA@mail.gmail.com>
Date: Tue, 15 Sep 2015 22:43:39 -0700
Message-ID: 
 <CABDss3hx4GYEiz1u9Dwa9_M9u=816uJD1VA7w=UB9R5X6tTi4w@mail.gmail.com>
Subject: Re: Data structures with topology changes
From: Alexey Goncharuk <alexey.goncharuk@gmail.com>
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary=001a1135b1dacf8414051fd6c7d8

--001a1135b1dacf8414051fd6c7d8
Content-Type: text/plain; charset=UTF-8

I did not check those particular tests after both ignite-264 and
ignite-1482 were fixed. There might be something else left to fix, I will
check the tests tomorrow and will create an additional ticket with proper
description if something comes up.

2015-09-15 21:10 GMT-07:00 Dmitriy Setrakyan <dsetrakyan@apache.org>:

> Igniters,
>
> I have come across IGNITE-1482 [1] which we have fixed in the upcoming 1.4
> release. The issue we have fixed had to do with IgniteCache.replace(...)
> operation not returning a correct value on cluster topology changes.
>
> But a comment in the ticket states that data structures, like AtomicLong,
> AtomicSequence, etc., may suffer from the same problem. If that is the
> case, have we fixed this issue for the data structures as well? If not, we
> should  probably create a new ticket for it and cross-link these 2 issues
> in Jira together.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-1482
>
> D.
>

--001a1135b1dacf8414051fd6c7d8--