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

[LTS] AMQ 7 should try to compact journals containing update records after repeated redelivery

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • None
    • None
    • None

    Description

      In cases where clients reject messages and get repeated redeliveries, the broker's journals can come to contain a huge number of update records. In the present journal compaction impleementation, these records cannot be removed so long as the message has not been delivered. So if a client is badly-behaved, journals will be added until storage is exhausted. The situation is made worse by the fact that the broker does not (perhaps can not) respect the max-disk-usage configuration in a situation like this.

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-4978 Performance of "Processing Latency" is reduced compare to AMQ 7.7 version

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

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-5187 AMQ 7 should try to compact journals containing update records after repeated redelivery

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

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-4817 AMQ 7 overflows its allocated storage and will not clean up

          • 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
          is related to

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-4830 AMQ 7 should mitigate dangerous redelivery configurations by default

          • 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

          Bug - A problem that impairs or prevents the functions of the product. ENTMQMAAS-2711 Please set journal-pool-files to a set file such as 10

          • 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

              csuconic@redhat.com Clebert Suconic
              rhn-support-kboone Kevin Boone
              Roman Vais Roman Vais
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: