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

Drainer task should be run as a job and not as unmanaged pod

    XMLWordPrintable

Details

    • Story
    • Resolution: Unresolved
    • Major
    • None
    • AMQ 7.9.3.GA
    • operator
    • None

    Description

      Currently during scale down drainer task is started as unmanaged pod and there no indication whether the drainer task has completed successful or not. Starting drainer as a job would allow to monitor its progress and see its outcome.

      Attachments

        Issue Links

          duplicates

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ENTMQBR-3575 Operator shouldn't remove Drainer pods right after them finishing

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

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-8106 AMQ Broker Drainer pod doesn't function properly after changing MessageMigration in CR

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

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ENTMQBR-3135 Drainer should get a debug mode

          • 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

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ENTMQBR-8583 [Docs] Drainer task should be run as a job and not as unmanaged pod

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

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ENTMQBR-8610 [Docs] Drainer task should be run as a job and not as unmanaged pod

          • 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

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ENTMQBR-5420 The drainer Must guarantee the delivery of the messages to the remaining broker in the cluster

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

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-8682 Message Migration can have duplicated messages

          • Critical - To be worked on immediately following BLOCKER issues.
          • In Progress
          relates to

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-8641 Interrupting message migration in action creates message duplicates across separate Targets

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

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ENTMQBR-3135 Drainer should get a debug mode

          • 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
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Activity

            People

              gaohoward Howard Gao
              rhn-support-toross Tom Ross
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated: