Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-14976

Ignite cache keys distribution tracker

    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 2.10
    • None
    • cache
    • None
    • Docs Required, Release Notes Required

    Description

      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.

      Attachments

        Activity

          People

            Unassigned Unassigned
            ivan.fedorenkov Ivan Fedorenkov
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: