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

ClusterExpirationManager missing locking

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 8.2.0.Beta2, 8.2.0.Final
    • 8.1.0.Final
    • Core
    • None

    Description

      Because ClusterExpirationManager.handleLifespanExpired() doesn't lock the entry and the value is actually read in the async thread, the created RemoveExpiredCommand sometimes uses a newer value written by another thread.

      Could be fixed by using DataContainer.compute() to check expiration and create the RemoveExpirationCommand.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. ISPN-5937 HotRod client ExpiryTest.testGlobalExpiryPutWithFlag random failures

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) ISPN-6050 RemoveExpiredCommand should check the version

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • To Do

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: