ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eduard Shangareev (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-8414) In-memory cache should use BLAT as their Affinity Topology
Date Fri, 27 Apr 2018 14:15:00 GMT

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

Eduard Shangareev updated IGNITE-8414:
--------------------------------------
    Labels: IEP-4 Phase-2  (was: )

> In-memory cache should use BLAT as their Affinity Topology
> ----------------------------------------------------------
>
>                 Key: IGNITE-8414
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8414
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Eduard Shangareev
>            Assignee: Eduard Shangareev
>            Priority: Major
>              Labels: IEP-4, Phase-2
>
> Now in-memory caches use all active server nodes as affinity topology and it changes
with each node join and exit. What differs from persistent caches behavior which uses BLAT
(BaseLine Affinity Topology) as their affinity topology.
> It causes problems:
> - we lose (in general) co-location between different caches;
> - we can't avoid PME when a non-BLAT node joins cluster;
> - implementation should consider 2 different approaches to affinity
> calculation.
> To handle these problems we should make in-memory and persistent cache work similar.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message