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

Transparent eager locking for transactions

    XMLWordPrintable

Details

    • Medium

    Description

      Allow a configuration attribute on <transaction /> to be able to specify whether cluster-wide locks are acquired eagerly or lazily. The current scheme (lazy) should be the default.

      This could be implemented by broadcasting LockControlCommands alongside acquiring local locks for necessary keys.

      Attachments

        Issue Links

          is blocked by

          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-48 Introduce lock() and unlock() API methods

          • 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

              vblagoje Vladimir Blagojevic (Inactive)
              manik_jira Manik Surtani (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: