[
https://issues.apache.org/jira/browse/IGNITE-3207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-3207:
--------------------------------
Description:
We have got a TON of questions on gridName property. Everyone thinks that
clusters are formed based on the gridName, that is, nodes with the same grid
name will join one cluster, and nodes with a different name will be in a
separate cluster.
Let's do the following:
* Deprecate IgniteConfiguration.gridName
* Add IgniteConfiguration.localInstanceName
* Rename related parameters in Ignition class (and other places, if present)
* Update Javadoc: clearly state that this name only works locally and has no
effect on topology.
2.0 migration guide has to be updated if needed:
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide
was:
We have got a TON of questions on gridName property. Everyone thinks that
clusters are formed based on the gridName, that is, nodes with the same grid
name will join one cluster, and nodes with a different name will be in a
separate cluster.
Let's do the following:
* Deprecate IgniteConfiguration.gridName
* Add IgniteConfiguration.localInstanceName
* Rename related parameters in Ignition class (and other places, if present)
* Update Javadoc: clearly state that this name only works locally and has no
effect on topology.
> Rename IgniteConfiguration.gridName
> -----------------------------------
>
> Key: IGNITE-3207
> URL: https://issues.apache.org/jira/browse/IGNITE-3207
> Project: Ignite
> Issue Type: Improvement
> Components: general
> Affects Versions: 1.1.4
> Reporter: Pavel Tupitsyn
> Assignee: Alexandr Fedotov
> Labels: important
> Fix For: 2.0
>
>
> We have got a TON of questions on gridName property. Everyone thinks that
> clusters are formed based on the gridName, that is, nodes with the same grid
> name will join one cluster, and nodes with a different name will be in a
> separate cluster.
> Let's do the following:
> * Deprecate IgniteConfiguration.gridName
> * Add IgniteConfiguration.localInstanceName
> * Rename related parameters in Ignition class (and other places, if present)
> * Update Javadoc: clearly state that this name only works locally and has no
> effect on topology.
> 2.0 migration guide has to be updated if needed:
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
