ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexei Scherbakov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-4448) Implement correct affinity validation on joining topology.
Date Thu, 06 Apr 2017 10:42:41 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alexei Scherbakov updated IGNITE-4448:
--------------------------------------
    Fix Version/s:     (was: 2.0)
                   2.1

> 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.1
>
>
> 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.15#6346)

Mime
View raw message