[
https://issues.apache.org/jira/browse/IGNITE-8794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16537216#comment-16537216
]
ASF GitHub Bot commented on IGNITE-8794:
----------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4270
> CPP Thin: Implement Best Effort Affinity
> ----------------------------------------
>
> Key: IGNITE-8794
> URL: https://issues.apache.org/jira/browse/IGNITE-8794
> Project: Ignite
> Issue Type: New Feature
> Components: platforms
> Affects Versions: 2.5
> Reporter: Igor Sapego
> Assignee: Igor Sapego
> Priority: Major
> Labels: cpp, iep-23
> Fix For: 2.7
>
>
> Implement Best Effort Affinity.
>
> The scenario is following:
> 1. Thin client connects to one of the node from the user provided address
> list.
> 2. When user create instance of CacheClient, thin client requests partition
> mapping for the cache.
> 3. Client establishes connections to nodes, which are both in the list,
> provided by user and in a server node response.
> 4. When user makes put/get/some other cache operation, thin client makes the
> best effort to send the request to the node, which stores the data.
> 5. To update partition mapping, thin client can provide public API, or do it
> with some timeout. Also, we can add "miss" flag to cache operation response,
> which will indicate, that operation was not local for the server node and
> which thin client can use to understand, that partition mapping has changed
> to request server node for an update.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
