ConsistentId for IgniteConfiguration

[Ira Vasilinets]

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.

[dsetrakyan]

Ira,

Can you please describe what a consistent ID is?

D.

On Tue, Jul 7, 2015 at 3:27 AM, Ira Vasilinets <[hidden email]>
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.
>

[Ira Vasilinets]

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 <[hidden email]>
wrote:

> Ira,
>
> Can you please describe what a consistent ID is?
>
> D.
>
> On Tue, Jul 7, 2015 at 3:27 AM, Ira Vasilinets <[hidden email]>
> 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-2]

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 <[hidden email]>
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 <[hidden email]>
> wrote:
>
> > Ira,
> >
> > Can you please describe what a consistent ID is?
> >
> > D.
> >
> > On Tue, Jul 7, 2015 at 3:27 AM, Ira Vasilinets <[hidden email]
> >
> > 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

[Ira Vasilinets]

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 <[hidden email]>
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 <[hidden email]>
> 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 <[hidden email]
> >
> > wrote:
> >
> > > Ira,
> > >
> > > Can you please describe what a consistent ID is?
> > >
> > > D.
> > >
> > > On Tue, Jul 7, 2015 at 3:27 AM, Ira Vasilinets <
> [hidden email]
> > >
> > > 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
>

[dsetrakyan]

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 <[hidden email]>
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 <[hidden email]>
> 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 <[hidden email]
> >
> > 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 <
> [hidden email]
> > >
> > > wrote:
> > >
> > > > Ira,
> > > >
> > > > Can you please describe what a consistent ID is?
> > > >
> > > > D.
> > > >
> > > > On Tue, Jul 7, 2015 at 3:27 AM, Ira Vasilinets <
> > [hidden email]
> > > >
> > > > 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
> >
>

[Yakov Zhdanov-2]

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 <[hidden email]>:

> 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 <[hidden email]>
> 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 <
> [hidden email]>
> > 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 <
> [hidden email]
> > >
> > > 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 <
> > [hidden email]
> > > >
> > > > wrote:
> > > >
> > > > > Ira,
> > > > >
> > > > > Can you please describe what a consistent ID is?
> > > > >
> > > > > D.
> > > > >
> > > > > On Tue, Jul 7, 2015 at 3:27 AM, Ira Vasilinets <
> > > [hidden email]
> > > > >
> > > > > 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
> > >
> >
>

[Atri Sharma]

I still don't understand why the consistent Id is needed honestly...
On 8 Jul 2015 20:49, "Yakov Zhdanov" <[hidden email]> 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 <[hidden email]>:
>
> > 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 <[hidden email]
> >
> > 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 <
> > [hidden email]>
> > > 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 <
> > [hidden email]
> > > >
> > > > 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 <
> > > [hidden email]
> > > > >
> > > > > wrote:
> > > > >
> > > > > > Ira,
> > > > > >
> > > > > > Can you please describe what a consistent ID is?
> > > > > >
> > > > > > D.
> > > > > >
> > > > > > On Tue, Jul 7, 2015 at 3:27 AM, Ira Vasilinets <
> > > > [hidden email]
> > > > > >
> > > > > > 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
> > > >
> > >
> >
>

[yzhdanov]

Consistent ID is involved in partition to node mappings. So if node
preserves its consistent ID during restarts it picks the same partitions.

--Yakov

2015-07-08 18:22 GMT+03:00 Atri Sharma <[hidden email]>:

> I still don't understand why the consistent Id is needed honestly...
> On 8 Jul 2015 20:49, "Yakov Zhdanov" <[hidden email]> 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 <[hidden email]>:
> >
> > > 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 <
> [hidden email]
> > >
> > > 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 <
> > > [hidden email]>
> > > > 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 <
> > > [hidden email]
> > > > >
> > > > > 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 <
> > > > [hidden email]
> > > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Ira,
> > > > > > >
> > > > > > > Can you please describe what a consistent ID is?
> > > > > > >
> > > > > > > D.
> > > > > > >
> > > > > > > On Tue, Jul 7, 2015 at 3:27 AM, Ira Vasilinets <
> > > > > [hidden email]
> > > > > > >
> > > > > > > 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
> > > > >
> > > >
> > >
> >
>

[Andrey Gura]

Probably it would be useful to be able set user defined consistent ID
generator. For example it can request consistent ID for node from remote
configuration server or generate it using specific user defined logic.

On Wed, Jul 8, 2015 at 6:19 PM, Yakov Zhdanov <[hidden email]> 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 <[hidden email]>:
>
> > 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 <[hidden email]
> >
> > 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 <
> > [hidden email]>
> > > 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 <
> > [hidden email]
> > > >
> > > > 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 <
> > > [hidden email]
> > > > >
> > > > > wrote:
> > > > >
> > > > > > Ira,
> > > > > >
> > > > > > Can you please describe what a consistent ID is?
> > > > > >
> > > > > > D.
> > > > > >
> > > > > > On Tue, Jul 7, 2015 at 3:27 AM, Ira Vasilinets <
> > > > [hidden email]
> > > > > >
> > > > > > 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
> > > >
> > >
> >
>

--
Andrey Gura
GridGain Systems, Inc.
www.gridgain.com

[Atri Sharma]

+1
On 8 Jul 2015 20:55, "Yakov Zhdanov" <[hidden email]> wrote:

> Consistent ID is involved in partition to node mappings. So if node
> preserves its consistent ID during restarts it picks the same partitions.
>
> --Yakov
>
> 2015-07-08 18:22 GMT+03:00 Atri Sharma <[hidden email]>:
>
> > I still don't understand why the consistent Id is needed honestly...
> > On 8 Jul 2015 20:49, "Yakov Zhdanov" <[hidden email]> 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 <[hidden email]>:
> > >
> > > > 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 <
> > [hidden email]
> > > >
> > > > 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 <
> > > > [hidden email]>
> > > > > 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 <
> > > > [hidden email]
> > > > > >
> > > > > > 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 <
> > > > > [hidden email]
> > > > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Ira,
> > > > > > > >
> > > > > > > > Can you please describe what a consistent ID is?
> > > > > > > >
> > > > > > > > D.
> > > > > > > >
> > > > > > > > On Tue, Jul 7, 2015 at 3:27 AM, Ira Vasilinets <
> > > > > > [hidden email]
> > > > > > > >
> > > > > > > > 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
> > > > > >
> > > > >
> > > >
> > >
> >
>

[dsetrakyan]

Yakov,

Can you provide example of how it will look?

D.

On Wed, Jul 8, 2015 at 8:19 AM, Yakov Zhdanov <[hidden email]> 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 <[hidden email]>:
>
> > 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 <[hidden email]
> >
> > 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 <
> > [hidden email]>
> > > 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 <
> > [hidden email]
> > > >
> > > > 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 <
> > > [hidden email]
> > > > >
> > > > > wrote:
> > > > >
> > > > > > Ira,
> > > > > >
> > > > > > Can you please describe what a consistent ID is?
> > > > > >
> > > > > > D.
> > > > > >
> > > > > > On Tue, Jul 7, 2015 at 3:27 AM, Ira Vasilinets <
> > > > [hidden email]
> > > > > >
> > > > > > 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
> > > >
> > >
> >
>