Uploaded image for project: 'Red Hat Data Grid'
  1. Red Hat Data Grid
  2. JDG-4188

Explicit Locks should throw AvailabilityException during ClusterPartition instead of Timeouts

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • None
    • RHDG 8.1 GA
    • API and Configuration, Clustering
    • None

    Description

      It seems that locks explicitly set by the application with lock(key) are not considered in case of active partition handling (the cache is in DEGRADED mode).

      In that case it will be still a timeout to aquire the lock, but it would be preferable to throw an AvailabilityException immediately instead of a TimeoutException after 30 seconds.

      The AvailabilityExcetpion is (only) thrown in case of put or get requests.

       

      Attachments

        Issue Links

          clones

          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-12484 Explicit Locks should throw AvailabilityException during ClusterPartition instead of Timeouts

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

          Activity

            People

              rh-ee-jbolina Jose Bolina
              rhn-support-wfink Wolf Fink
              Gustavo Lira Silva Gustavo Lira Silva
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: