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.
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
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:
We can add 'nodeName' on ClusterNode API, it is very easy to implement
since node name is already stored in node attributes.
On Wed, Aug 26, 2015 at 4:44 AM, Dmitriy Setrakyan dsetrak...@apache.org
wrote:
Although I share the sentiment that gridName is confusing, I think renaming
gridName to
+1 for 'instanceName'. 'nodeName' looks confusing as well - I would think
that it should be unique among all nodes.
-Val
On Wed, Aug 26, 2015 at 2:25 AM, Raul Kripalani r...@evosent.com wrote:
Agree. The term grid to refer to a single node is very confusing.
On 19 Aug 2015 08:58, Semyon
