You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Daschinskiy (Jira)" <ji...@apache.org> on 2021/03/30 17:34:00 UTC
[jira] [Commented] (IGNITE-14444) Move affinity calculation and
storage to client
[ https://issues.apache.org/jira/browse/IGNITE-14444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17311680#comment-17311680 ]
Ivan Daschinskiy commented on IGNITE-14444:
-------------------------------------------
[~isapego] Hi, patch is ready for review
> Move affinity calculation and storage to client
> -----------------------------------------------
>
> Key: IGNITE-14444
> URL: https://issues.apache.org/jira/browse/IGNITE-14444
> Project: Ignite
> Issue Type: Improvement
> Components: python
> Affects Versions: python-0.4.0
> Reporter: Ivan Daschinskiy
> Assignee: Ivan Daschinskiy
> Priority: Major
> Labels: python
> Fix For: python-0.4.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In current implementation, affinity storage and affinity calculation are located in cache.
> It is not optimal:
> 1. affinity is not shared between Cache instance with same name
> 2. affinity mapping requests per cache and add additional loads.
> 3. if we start implementing transactions or expiry policy, this can be an issue.
> I propose to move affinity storage to Client and AioClient.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)