[
https://issues.apache.org/jira/browse/IGNITE-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647459#comment-14647459
]
Andrey Gura edited comment on IGNITE-1016 at 7/30/15 10:51 AM:
---------------------------------------------------------------
Dmitry, the import part of Valentin's comments is "when possible". Current
implementation of {{RendezvousAffinityFunction}} tries to assign partitions to
backups that deployed to different hosts, but if it is impossible then node on
the same host can be assigned as backup to the partition.
So I think that {{excludeNeighbors}} with default value {{true}} it's good idea
for all affinity functions.
was (Author: agura):
Dmitry, the import part of Valentin's comments is "when possible". Current
implementation of {{RendezvousAffinityFunction}} tries to assign partitions to
backups that deployed to different hosts, but if it is impossible then node on
the same host can be assigned as backup to the partition.
So I think that {{excludeNeighbors}} with default value {{true}} it is good
idea.
> Add excludeNeighbors and backupFilter to FairAffinityFunction
> -------------------------------------------------------------
>
> Key: IGNITE-1016
> URL: https://issues.apache.org/jira/browse/IGNITE-1016
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: sprint-4
> Reporter: Valentin Kulichenko
> Assignee: Andrey Gura
> Labels: Usability
> Fix For: sprint-7
>
>
> These properties are currently available only for
> {{RendezvousAffinityFunction}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
