Mailing-List: contact user-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@ignite.apache.org
MIME-Version: 1.0
Sender: anirudha81@gmail.com
In-Reply-To: <1510089178222-0.post@n6.nabble.com>
References: <1499696682563-14590.post@n6.nabble.com> <1509989831194-0.post@n6.nabble.com>
 <1510014390467-0.post@n6.nabble.com> <1510070979040-0.post@n6.nabble.com>
 <1510073862287-0.post@n6.nabble.com> <1510083102548-0.post@n6.nabble.com> <1510089178222-0.post@n6.nabble.com>
From: Anirudha Jadhav <anirudha@nyu.edu>
Date: Tue, 7 Nov 2017 20:47:54 -0500
Message-ID: <CAG7XKRgY7-gbCB7wA6EdsE0FquTGX9QWe5_KigDBJSDUpeb_eQ@mail.gmail.com>
Subject: Re: split-brain problem and GridSegmentationProcessor
To: user@ignite.apache.org
Content-Type: multipart/alternative; boundary="001a113cf8b82217c3055d6ee28f"
archived-at: Wed, 08 Nov 2017 01:54:24 -0000

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

we are just in the works of using a separate  zk cluster to provide an
implementation for segmentation resolution. If anyone else is working on it
we could collaborate.

or create a separate jira for a design review? what do you guys think? i
think we could also make zk itself pluggable

-Ani

On Tue, Nov 7, 2017 at 4:12 PM, luqmanahmad <luqmanahmed@gmail.com> wrote:

> Hi Amit,
>
> Correct you have to provide implementation for both.
>
> Your custom segmentation will just be validating something and that method
> of your segmentation resolver will be called inside the implementation of
> GridSegmentationProcess which can be overriden through your plugin. By
> default GridOsSegmentationProcessor is returning true and missing the whole
> logic of validating different resolvers.
>
> Makes sense ?
>
> Thanks,
> Luqman
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


-- 
Anirudha P. Jadhav

--001a113cf8b82217c3055d6ee28f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">we are just in the works of using a separate=C2=A0 zk clus=
ter to provide an implementation for segmentation resolution. If anyone els=
e is working on it we could collaborate.<br><br>or create a separate jira f=
or a design review? what do you guys think? i think we could also make zk i=
tself pluggable<br><br>-Ani</div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Tue, Nov 7, 2017 at 4:12 PM, luqmanahmad <span dir=3D"l=
tr">&lt;<a href=3D"mailto:luqmanahmed@gmail.com" target=3D"_blank">luqmanah=
med@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Am=
it,<br>
<br>
Correct you have to provide implementation for both.<br>
<br>
Your custom segmentation will just be validating something and that method<=
br>
of your segmentation resolver will be called inside the implementation of<b=
r>
GridSegmentationProcess which can be overriden through your plugin. By<br>
default GridOsSegmentationProcessor is returning true and missing the whole=
<br>
logic of validating different resolvers.<br>
<br>
Makes sense ?<br>
<br>
Thanks,<br>
Luqman<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
<br>
--<br>
Sent from: <a href=3D"http://apache-ignite-users.70518.x6.nabble.com/" rel=
=3D"noreferrer" target=3D"_blank">http://apache-ignite-users.<wbr>70518.x6.=
nabble.com/</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
<div class=3D"gmail_signature" data-smartmail=3D"gmail_signature">Anirudha =
P. Jadhav<br></div>
</div>

--001a113cf8b82217c3055d6ee28f--