ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexandr Fedotov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3207) Rename IgniteConfiguration.gridName
Date Wed, 28 Dec 2016 11:59:58 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-3207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15782751#comment-15782751
] 

Alexandr Fedotov commented on IGNITE-3207:
------------------------------------------

Looks like there has not been any activity since July. Taking the issue.

> 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
>              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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message