ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: ConsistentId for IgniteConfiguration
Date Thu, 09 Jul 2015 08:54:59 GMT
Yakov,

Can you provide example of how it will look?

D.

On Wed, Jul 8, 2015 at 8:19 AM, Yakov Zhdanov <yzhdanov@gridgain.com> wrote:

> I think that this should be added to configuration so user has opportunity
> to override auto assigned one since in case you change ifconfig of the host
> or add/remove network card consistent ID will be changed and node launched
> on the host will not pick up the same partitions as before.
>
>
> --
> Yakov Zhdanov, Director R&D
> *GridGain Systems*
> www.gridgain.com
>
> 2015-07-07 20:48 GMT+03:00 Dmitriy Setrakyan <dsetrakyan@apache.org>:
>
> > To my knowledge, nodes are already started with consistent hash code used
> > for affinity, which survives restarts. Can someone clarify why we need
> the
> > consistent ID as well?
> >
> > D.
> >
> > On Tue, Jul 7, 2015 at 5:45 AM, Ira Vasilinets <ivasilinets@gridgain.com
> >
> > wrote:
> >
> > > Alexey,
> > >
> > > I do not want to remove default implementation of consistentId. If user
> > > would like to configure consistentId, he should write xml file per
> node.
> > > I will be glad if someone propose more elegant solution =)
> > >
> > > On Tue, Jul 7, 2015 at 2:07 PM, Alexey Kuznetsov <
> > akuznetsov@gridgain.com>
> > > wrote:
> > >
> > > > Ira, usually we have xml file with node config and start several
> nodes.
> > > > What would happened if user specify consistent id in spring xml file
> > and
> > > > start several nodes with same config?
> > > > Or in this case user should write as much xml files as much nodes he
> > > going
> > > > to start?
> > > >
> > > >
> > > > On Tue, Jul 7, 2015 at 6:00 PM, Ira Vasilinets <
> > ivasilinets@gridgain.com
> > > >
> > > > wrote:
> > > >
> > > > > ClusterNode.consistentId is consistent globally unique node ID and
> > > should
> > > > > be the same after node restart. Node consistent id is a string that
> > > > > contains node's addresses and port discovery number by default.
> After
> > > > > restarting node default consistentId could change. I think that
> > > > > IgniteConfiguration should have possibility to configurate constant
> > > > node's
> > > > > consistentId.
> > > > >
> > > > > On Tue, Jul 7, 2015 at 1:31 PM, Dmitriy Setrakyan <
> > > dsetrakyan@apache.org
> > > > >
> > > > > wrote:
> > > > >
> > > > > > Ira,
> > > > > >
> > > > > > Can you please describe what a consistent ID is?
> > > > > >
> > > > > > D.
> > > > > >
> > > > > > On Tue, Jul 7, 2015 at 3:27 AM, Ira Vasilinets <
> > > > ivasilinets@gridgain.com
> > > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Hi!
> > > > > > >
> > > > > > > I looked throught IgniteConfiguration methods and noticed
that
> we
> > > do
> > > > > not
> > > > > > > have posibility to configure node consistentId. I think
> > > > > > IgniteConfiguration
> > > > > > > should have methods setConsistentId and getConsistentId.
> > > > > > >
> > > > > > > Thoughts?
> > > > > > >
> > > > > > > Kind Regards,
> > > > > > > Ira.
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Alexey Kuznetsov
> > > > GridGain Systems
> > > > www.gridgain.com
> > > >
> > >
> >
>

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