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

Expiration Reaper thread should have a configuration to tweak priority

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • RHDG 8.1 GA
    • None
    • None
    • 0
    • 0% 0%

    Description

      With massive load and huge number of expirations the reaper might not able to handle the removal of expired entries fast enough to prevent from issues like OutOfMemory.
      There should be a configuration to tweak the thread priority and maybe the number of threads handling it. Also the thread should not use the general pool which might run out of threads for this under load.

      Attachments

        Issue Links

          incorporates

          Bug - A problem that impairs or prevents the functions of the product. JDG-3366 Transactional cache will slow down the expiration reaper

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • 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) JDG-3205 Cluster Expiration 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
          is incorporated by

          Feature Request - Feature requests from customers and/or users JDG-4421 Expiration Reaper should use multiple threads

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • New
          is related to

          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-10677 Expiration Reaper thread should have a better name than "pool-#-thread-#"

          • 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.
          • New
          links to

          Web Link KCS article

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: