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 Fedorenkov (Jira)" <ji...@apache.org> on 2021/06/23 11:07:00 UTC

[jira] [Created] (IGNITE-14976) Ignite cache keys distribution tracker

Ivan Fedorenkov created IGNITE-14976:
----------------------------------------

             Summary: Ignite cache keys distribution tracker
                 Key: IGNITE-14976
                 URL: https://issues.apache.org/jira/browse/IGNITE-14976
             Project: Ignite
          Issue Type: New Feature
          Components: cache
    Affects Versions: 2.10
            Reporter: Ivan Fedorenkov


Based on the Apache Ignite Summit presentation.

There is a use-case when a user may want to keep track of the up-to-date subset of cache keys that a node is responsible for. For example, if each node must subscribe in external system on updates, but only for those cache keys that the node is responsible for (primary or backup).

Why can't an external system use Ignite Data Streamer or Cache puts? Because this is impossible for many legacy systems or systems where user can't control the source of events (e.g. some web service).

Why is this useful? Data locality principle for subscriptions. Reduces the amount of network traffic.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)