ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prachi Garg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-10135) Documentation link to ClusterNodeAttributeAffinityBackupFilter
Date Tue, 06 Nov 2018 04:12:00 GMT

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

Prachi Garg commented on IGNITE-10135:
--------------------------------------

[~syssoftsol], could you provide an example for the configuration?

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

Mime
View raw message