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

JDBC Purge consistency issues

    XMLWordPrintable

Details

    Description

      The JdbcStringBasedStore's purge method requires the following enhancements:

      1. The connection should be enrolled in a transaction via autoCommit(false) with commit/rollback.
      2. Implementations of TableManager#getSelectOnlyExpiredRowsSql should utilise a SELECT ... FOR UPDATE statement to ensure that the expired entries are locked throughout the Tx

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. ISPN-11101 Purge on JDBC shared stores can cause deadlocks

          • 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.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. ISPN-11110 JdbcStringBasedStore Purge should not use FOR UPDATE to avoid excessive locking

          • 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.
          • Closed

          Activity

            People

              remerson@redhat.com Ryan Emerson
              remerson@redhat.com Ryan Emerson
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: