Re: Deprecate IgniteConfiguration.getGridName

[bintisepaha <bi...@tudor.com>]

Hi, 
We are facing this issue, nodes with different grid names are being
identified in a single topology.
Did the fix for this make it into version 1.6? If yes, how can I get this
version?

Thanks,
Binti



--
View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Deprecate-IgniteConfiguration-getGridName-tp2420p7613.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

Re: Deprecate IgniteConfiguration.getGridName

[bintisepaha <bi...@tudor.com>]

Thank you Val, this is very helpful.



--
View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Deprecate-IgniteConfiguration-getGridName-tp2420p7685.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

Re: Deprecate IgniteConfiguration.getGridName

[Valentin Kulichenko <va...@gmail.com>]

Binti,

This is not an issue. What is discussed here is just proper naming of this
configuration property, but the concept stays the same - this is the name
of local Ignite instance and there is no requirement for all nodes in
topology to share the same name.

Whether nodes discover each other or not is defined by discovery
configuration:
https://apacheignite.readme.io/docs/cluster-config#isolated-ignite-clusters-on-the-same-set-of-machin

-Val

On Fri, Feb 26, 2016 at 7:19 AM, bintisepaha <bi...@tudor.com> wrote:

> Hi,
> We are facing this issue, nodes with different grid names are being
> identified in a single topology.
> Did the fix for this make it into version 1.6? If yes, how can I get this
> version?
>
> Thanks,
> Binti
>
>
>
> --
> View this message in context:
> http://apache-ignite-developers.2346864.n4.nabble.com/Deprecate-IgniteConfiguration-getGridName-tp2420p7613.html
> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
>