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

L1 expiration should not touch stores or other nodes

    XMLWordPrintable

Details

    • Bug
    • Status: New (View Workflow)
    • Major
    • Resolution: Unresolved
    • 13.0.0.Dev03, 12.1.7.Final
    • None
    • Core, L1
    • None
    • Hide

      L1 expi

      Show
      L1 expi
    • ---
    • ---

    Description

      When L1 entries expire, they use the same expiration logic that regular lifespan expiration uses.

      But L1 entries are only stored in the data container, and the lifespan is different on each node, so L1 entry expiration should be a lot less expensive than regular lifespan expiration.

      We also need a test for L1 expiration in the core test suite. Regular lifespan expiration tests were probably enough before lifespan expiration became clustered, but L1 is different enough that it should have its own tests.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated: