[
https://issues.apache.org/jira/browse/IGNITE-10135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707711#comment-16707711
]
Prachi Garg commented on IGNITE-10135:
--------------------------------------
[[email protected]], please review the 3rd paragraph in the in "Crash-safe
Affinity" callout -
[https://apacheignite.readme.io/v2.6/docs/affinity-collocation-27#section-affinity-function|https://apacheignite.readme.io/v2.6/docs/affinity-collocation-27#section-affinity-function.]
> Documentation link to ClusterNodeAttributeAffinityBackupFilter
> --------------------------------------------------------------
>
> Key: IGNITE-10135
> URL: https://issues.apache.org/jira/browse/IGNITE-10135
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
> Reporter: David Harvey
> Assignee: Prachi Garg
> Priority: Major
> Fix For: 2.7
>
>
> IGNITE-9365 adds ClusterNodeAttributeAffinityBackupFilter to allow
> "Crash-safe Affinity"
> ([https://apacheignite.readme.io/docs/affinity-collocation|https://apacheignite.readme.io/docs/affinity-collocation_])
> to be configured from spring.
> The class should have an adequate description of how to set this up, but the
> above section should link to or otherwise flag that such a procedure exist.
> [https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/cache/affinity/rendezvous/ClusterNodeAttributeAffinityBackupFilter.java]
>
> Note: the implementation is generic, allowing any node attribute (or
> environment variable) to be configured so that primary and backup's are
> always forced to not be on the same node.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
