ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Goncharuk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-1016) Add excludeNeighbors and backupFilter to FairAffinityFunction
Date Wed, 09 Sep 2015 00:56:45 GMT

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

Alexey Goncharuk commented on IGNITE-1016:
------------------------------------------

Andrey, {{force}} update is used as a fallback mechanism to make sure that nodes are evenly
loaded even in the case when no non-moving partition assignments can be made. Can you add
a specialized test when all nodes are resided on one host and exludeNeighbors = true, and
then check that nodes are evenly loaded and there are no missed partitions? It is not possible
to assign partitions to non-neighbors if there are fewer _hosts_ in a grid than the number
of configured backups. I want to make sure that in this case we still have the required number
of partitions in any assignment.

> 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: Valentin Kulichenko
>              Labels: Usability
>             Fix For: ignite-1.4
>
>         Attachments: ignite-1016.patch, ignite-1016.patch
>
>
> These properties are currently available only for {{RendezvousAffinityFunction}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message