Mailing-List: contact dev-help@ignite.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAGcMBHibXsME2TjJ6+k2X=Q4K8HHiswML7Zhuwanit0HZFqg6A@mail.gmail.com>
References: 
 <CAGcMBHibXsME2TjJ6+k2X=Q4K8HHiswML7Zhuwanit0HZFqg6A@mail.gmail.com>
From: Dmitriy Setrakyan <dsetrakyan@apache.org>
Date: Sat, 7 Mar 2015 20:00:37 -0800
Message-ID: 
 <CA+0=VoXkPtGOZ05BxMXAN=WC+MGkTkkrPBbGH5iXyeoe4nX4Uw@mail.gmail.com>
Subject: Re: cache topology validator
To: "dev@ignite.incubator.apache.org" <dev@ignite.incubator.apache.org>
Content-Type: multipart/alternative; boundary=089e01538a5434374d0510bef84f

--089e01538a5434374d0510bef84f
Content-Type: text/plain; charset=UTF-8

+1

I think we should create a ticket for it and pick it up in sprint-3 or
sprint-4.

D.

On Fri, Mar 6, 2015 at 5:26 AM, Yakov Zhdanov <yzhdanov@apache.org> wrote:

> Guys,
>
> I think we should provide user with ability to validate cache topology
> before each cache operation.
>
> Now user cannot validate the topology of cache update, but this seems to be
> a good feature. I can validate task topology and throw exception on MAP
> step, but I cannot do that on cache put.
>
> I suggest introducing special topology validator. Whenever cache topology
> changes - it is passed to validator. Validator can check nodes number and
> presence of particular (if user have servers with special role in
> topology), this also may be used to validate segment local node operates
> in. If cache topology is not valid each cache update throws exception until
> cache topology does not become valid back.
>
> --Yakov
>

--089e01538a5434374d0510bef84f--