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

Cluster Expiration should only expire primary owned entries

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • RHDG 7.3.4 ER1
    • JDG 7.3 GA
    • Clustering
    • None
    • DataGrid Sprint #35, DataGrid Sprint #36

    Description

      Today cluster expiration fires for any expired entry it finds. We should instead only expire an entry when it is the primary owner encountering the entry. This will allow expiration to scale much better depending on the number of owners. This also reduces network and locking contention as we may have been sending duplicate expiration commands from backups and primary at the same time.

      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-10678 Cluster Expiration Reaper should only expire primary owned entries

          • 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
          incorporates

          Bug - A problem that impairs or prevents the functions of the product. ISPN-10696 Cluster Expiration reaper limits parallel expirations too much

          • 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 incorporated by

          Feature Request - Feature requests from customers and/or users JDG-3388 Expiration Reaper thread should have a configuration to tweak priority

          • 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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JDG-3209 Massive Expiration can not be handled by the reaper without backlog and cause OutOfMemory

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

          Web Link Expiration process change in RHDG 7.3 CP 4 KCS

          Activity

            People

              wburns@redhat.com Will Burns
              rhn-support-wfink Wolf Fink
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: