Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-5192

Aggressive caching of paged messages

    XMLWordPrintable

Details

    Description

      The current broker implementation is optimized for delivery of messages. As a result current paging implementation is aggressively caching paged messages and it works well with a small number of paged queues. But in use cases where there are thousands of paging queues the JVM memory requirements become unsustainable. For a example for 1000 paging queues the current implementation requires about 60GB of memory just for caching.
      The broker should offer ways of configuring/limiting the size of those caches.

      Attachments

        Issue Links

          is cloned by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ENTMQBR-7367 [Docs] Aggressive caching of paged messages

          • 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

          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) AMQDOC-3261 Document cost of paging

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

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-6743 Inaccurate Paging Counts causes Broker to Page with Less than max-size-bytes worth of Messages

          • 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

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-7145 Inaccurate Paging Counts causes Broker to Page with Less than max-size-bytes worth of Messages

          • 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

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-7867 [LTS] Inaccurate Paging Counts causes Broker to Page with Less than max-size-bytes worth of Messages

          • 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

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-7427 AMQ must start cleanly in reasonable time and with modest memory, however large the journal

          • Undefined - Priority not specified.
          • Closed
          links to

          Web Link WARN [org.apache.activemq.artemis.utils.actors.OrderedExecutor] Java heap space: java.lang.OutOfMemoryError: Java heap space

          mentioned in

          Page Loading...

          Activity

            People

              csuconic@redhat.com Clebert Suconic
              rhn-support-toross Tom Ross
              Tiago Bueno Tiago Bueno
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: