[
https://issues.apache.org/jira/browse/IGNITE-3207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356931#comment-15356931
]
ASF GitHub Bot commented on IGNITE-3207:
----------------------------------------
GitHub user f7753 opened a pull request:
https://github.com/apache/ignite/pull/842
IGNITE-3207 Rename IgniteConfiguration.gridName
- 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.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/f7753/ignite ignite-3207
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/842.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #842
----
----
> 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: Biao Ma
> Fix For: 1.7
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
