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

Operator does not automatically deploy CRD created addresses on scale-up

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Critical
    • AMQ 7.7.0.CR1
    • AMQ 7.5.0.GA
    • operator
    • None
    • Hide
      In prior releases, if you used a Custom Resource (CR) instance to create addresses in an Operator-based broker deployment, and then scaled up the size of that deployment, the Operator did not automatically deploy existing addresses to the new broker instances. Instead, you needed to delete the address CR, before redeploying the CR for the scaled-up broker deployment. This issue is now resolved. When you scale up the size of a broker deployment, the Operator automatically deploys existing addresses to the new broker instances.
      Show
      In prior releases, if you used a Custom Resource (CR) instance to create addresses in an Operator-based broker deployment, and then scaled up the size of that deployment, the Operator did not automatically deploy existing addresses to the new broker instances. Instead, you needed to delete the address CR, before redeploying the CR for the scaled-up broker deployment. This issue is now resolved. When you scale up the size of a broker deployment, the Operator automatically deploys existing addresses to the new broker instances.
    • Documented as Resolved Issue

    Description

      Actually, when we need to scale-up an Openshift AMQ cluster (deployed using Operators) the new broker doesn't have any configuration of the already running brokers [related to addresses]. For example, we need to manually redeploy the addresses so the new broker can start to receive messages. The process is to remove the addresses from the cluster and them recreate them .

      There're some drawbacks of this approach:
      1. We can't really automatically scale-up the AMQ cluster.
      2. The scale-up process should be simple in Openshift, which isn't.
      3. ENTMQBR-3383

      I think it's a good idea to re-think and improve the scale up process in this subject.

      Attachments

        Issue Links

          is cloned by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ENTMQBR-3723 Porting ENTMQBR-3137 to LTS

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

          Task - Represents a small unit of work that is not end-user facing. ENTMQBR-3480 Doc: [OCP] Operator does not automatically deploy CRD created addresses on scale-up

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

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-3130 Broker operator doesn't recreate Address after broker redeploy

          • 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-3514 Address not created if address CR is submitted before broker instantiated

          • 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. ENTMQBR-3383 Deletion of address custom resource instance removes address and messages

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

          Activity

            People

              gaohoward Howard Gao
              Asouza@redhat.com Angelo Souza
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: