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

Invalidation mode needs a proper key partitioner

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 10.1.0.Final
    • 9.4.16.Final, 10.0.0.Final
    • Core
    • None

      Caches in invalidation mode used to do everything on the local node and only broadcast an invalidation command to all the members. ISPN-10029 changed this, and now transactional invalidation caches acquire locks for affected keys on the primary owners.

      Unfortunately KeyPartitionerFactory constructs a SingleSegmentKeyPartitioner in invalidation mode, so there is only one primary owner for all the keys.

              dberinde@redhat.com Dan Berindei (Inactive)
              dberinde@redhat.com Dan Berindei (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: