Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-1830

L1: On topology changes lose key requestors information

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Blocker
    • Resolution: Duplicate Issue
    • 5.1.0.FINAL
    • 5.2.0.CR1
    • Core
    • None

    Description

      I think we are losing information about where a key needs to be invalidated when a node changes from owner to non-owner (e.g. because another node joined):

      • We lose the list of requestors stored on this node. Even if all ClusteredGetCommands reached all the current owners (which we are about to change with ISPN-825), once all the current owners leave the new owners will not know about this node's old requestors.
      • We don't add ourselves as a requestor for the key on the new owners when we invalidate the entry and move it to L1.

      Attachments

        Issue Links

          Activity

            People

              dberinde@redhat.com Dan Berindei
              dberinde@redhat.com Dan Berindei
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: