Mailing-List: contact user-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <1469416169525-6499.post@n6.nabble.com>
References: <1469097836448-6442.post@n6.nabble.com> <CABDss3jY0Pk6Y=YsXti_GyieTKXOz-8B7etrefEB7kXZS5MP4w@mail.gmail.com>
 <1469160612029-6461.post@n6.nabble.com> <1469214191329-6477.post@n6.nabble.com>
 <1469290360028-6491.post@n6.nabble.com> <1469416169525-6499.post@n6.nabble.com>
From: Alexey Goncharuk <alexey.goncharuk@gmail.com>
Date: Tue, 26 Jul 2016 20:35:51 +0300
Message-ID: <CABDss3iFs6BWNWyFGcEYpFq14axUps1vpysXzz7LDWYwbwpZPQ@mail.gmail.com>
Subject: Re: How to use the logger in the BackupFilter?
To: user@ignite.apache.org
Content-Type: multipart/alternative; boundary=001a11440bde056d4e05388d55cf
archived-at: Tue, 26 Jul 2016 17:35:58 -0000

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

Jason,

As far as I understood your use case, machine-to group assignment (the
digit in your example) is constant and cannot change over time. In this
case user attributes should work perfectly like Val suggested.

If, for some reason, this does not meet your requirements, my suggestion
would be to implement an IgnitePlugin and create a component which
maintains this mapping. Ignite has an internal mechanism to exchange
arbitrary node information for it's components at the time of node
discovery. Take a look
at org.apache.ignite.internal.GridComponent#collectDiscoveryData
and org.apache.ignite.internal.GridComponent#onDiscoveryDataReceived. This
should be enough for you to implement virtually any strategy for affinity
assignment. Let us know if you need help with plugin development.

Thanks,
AG

2016-07-25 6:09 GMT+03:00 Jason <fqyang@outlook.com>:

> hi Val,
>
> Another question about point 3:
> Event with user attributes, but when do the deployment of adding new
> machines to the node, it will roll out one machine group by one, so this
> means during the period of deployment, all the nodes cannot get the same
> user attributes (machines group info) and if the Rendezvous hashing return
> a
> new machine list for one partition with a new machine in the top N (N is
> the
> backup # + 1), the backup filter in different nodes may made different
> decision.
>
> E.g. for partition p of cache c, its node list after Rendezvous hashing is
> A1, X1, B2, C3, D2, ..., where letter is machine and digit is group; and X
> is a new added machine and for rolled machine, its group is 1 but for
> others, it's unknown; and suppose the backup = 2. Say, we've rolled out
> group 1 and are rolling out group 2 now, so in machine A, it selects (A1,
> B2, C3), but in machine C, it may select (A1, X, B2), because it doesn't
> know which group X belongs to now. This will cause inconsistency.
>
> And we must ensure no data loss in the memory only.
>
> BTW, do you have any successful case for this usage scenario? how do you
> resolve this problem?
>
> Thanks,
> -Jason
>
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/How-to-use-the-logger-in-the-BackupFilter-tp6442p6499.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

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

<div dir=3D"ltr">Jason,<div><br></div><div>As far as I understood your use =
case, machine-to group assignment (the digit in your example) is constant a=
nd cannot change over time. In this case user attributes should work perfec=
tly like Val suggested.</div><div><br></div><div>If, for some reason, this =
does not meet your requirements, my suggestion would be to implement an Ign=
itePlugin and create a component which maintains this mapping. Ignite has a=
n internal mechanism to exchange arbitrary node information for it&#39;s co=
mponents at the time of node discovery. Take a look at=C2=A0org.apache.igni=
te.internal.GridComponent#collectDiscoveryData and=C2=A0org.apache.ignite.i=
nternal.GridComponent#onDiscoveryDataReceived. This should be enough for yo=
u to implement virtually any strategy for affinity assignment. Let us know =
if you need help with plugin development.=C2=A0</div><div><br></div><div>Th=
anks,</div><div>AG</div></div><div class=3D"gmail_extra"><br><div class=3D"=
gmail_quote">2016-07-25 6:09 GMT+03:00 Jason <span dir=3D"ltr">&lt;<a href=
=3D"mailto:fqyang@outlook.com" target=3D"_blank">fqyang@outlook.com</a>&gt;=
</span>:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">hi Val,<br>
<br>
Another question about point 3:<br>
Event with user attributes, but when do the deployment of adding new<br>
machines to the node, it will roll out one machine group by one, so this<br=
>
means during the period of deployment, all the nodes cannot get the same<br=
>
user attributes (machines group info) and if the Rendezvous hashing return =
a<br>
new machine list for one partition with a new machine in the top N (N is th=
e<br>
backup # + 1), the backup filter in different nodes may made different<br>
decision.<br>
<br>
E.g. for partition p of cache c, its node list after Rendezvous hashing is<=
br>
A1, X1, B2, C3, D2, ..., where letter is machine and digit is group; and X<=
br>
is a new added machine and for rolled machine, its group is 1 but for<br>
others, it&#39;s unknown; and suppose the backup =3D 2. Say, we&#39;ve roll=
ed out<br>
group 1 and are rolling out group 2 now, so in machine A, it selects (A1,<b=
r>
B2, C3), but in machine C, it may select (A1, X, B2), because it doesn&#39;=
t<br>
know which group X belongs to now. This will cause inconsistency.<br>
<br>
And we must ensure no data loss in the memory only.<br>
<br>
BTW, do you have any successful case for this usage scenario? how do you<br=
>
resolve this problem?<br>
<br>
Thanks,<br>
-Jason<br>
<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href=3D"http://apache-ignite-users.70518.x=
6.nabble.com/How-to-use-the-logger-in-the-BackupFilter-tp6442p6499.html" re=
l=3D"noreferrer" target=3D"_blank">http://apache-ignite-users.70518.x6.nabb=
le.com/How-to-use-the-logger-in-the-BackupFilter-tp6442p6499.html</a><br>
<div class=3D"HOEnZb"><div class=3D"h5">Sent from the Apache Ignite Users m=
ailing list archive at Nabble.com.<br>
</div></div></blockquote></div><br></div>

--001a11440bde056d4e05388d55cf--