You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/12/22 12:49:58 UTC
[jira] [Updated] (IGNITE-4448) Implement correct affinity
validation on joining topology.
[ https://issues.apache.org/jira/browse/IGNITE-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-4448:
------------------------------------
Fix Version/s: (was: 2,0)
2.0
> Implement correct affinity validation on joining topology.
> ----------------------------------------------------------
>
> Key: IGNITE-4448
> URL: https://issues.apache.org/jira/browse/IGNITE-4448
> Project: Ignite
> Issue Type: Improvement
> Components: cache
> Reporter: Alexei Scherbakov
> Assignee: Alexei Scherbakov
> Fix For: 2.0
>
>
> Currently on joining a topology only affinity class name and partition number are checked between configurations of local and remote nodes.
> This is not enough in case of configured backup filter and possible extension with primary filter and can lead to disastrous situations due to node misconfiguration.
> We should implement something like {{AffinityValidator}} having signature as follows:
> {noformat}
> boolean validate(Affinity affinity)
> {noformat}
> Maybe it'll be useful for other grid objects as well, like {{CacheStore}},{{NodeFilter}}, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)