Uploaded image for project: 'Cloud Enablement'
  1. Cloud Enablement
  2. CLOUD-2239

[EAP] Check that A-MQ resources are recovered on scaling down of pods

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • EAP71 1.0.0.GA
    • Documentation, EAP7
    • None
    • Documentation (Ref Guide, User Guide, etc.)

    Description

      When scaling down pods it is possible for transactions to remain in their prepared state. There is an automated procedure for recovering these (see CLOUD-2210) but there should also be a manual procedure for those cases where automatic recovery fails. The manual procedure for database resources is covered in CLOUD-2238 and a similar document is required for A-MQ resources that are enlisted in an XA transaction.

      There is already a solution within A-MQ to migrate messages on scale down and this may be sufficient but it does need verifying and/or documenting.

      Attachments

        Issue Links

          documents

          Bug - A problem that impairs or prevents the functions of the product. CLOUD-2210 [EAP] Support transaction recovery on scaling down of pods

          • 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.
          • Verified
          is incorporated by

          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) CLOUD-2243 Sprint 13 release

          • 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

          Task - Represents a small unit of work that is not end-user facing. CLOUD-2238 Document the manual procedure for resolving in doubt transactions

          • 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

          Activity

            People

              Unassigned Unassigned
              rhn-engineering-mmusgrov Michael Musgrove
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: