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

[EAP] Support transaction recovery on scaling down of pods

    XMLWordPrintable

Description

    When scaling down pods it is possible for transactions to remain in their prepared state, we need to support the ability to recover these transactions and either commit or rollback the transaction.

    We can use the approach already used within A-MQ to migrate messages on scale down, this allows an associated container to recover the transactions and attempt to complete them.

    Note that this is not intended to address scaling down of servers with subordinate transactions (e.g. JTS or JBoss Remoting) as per CLOUD-2262 that is not yet tested or supported.

    Attachments

      Issue Links

        causes

        Bug - A problem that impairs or prevents the functions of the product. CLOUD-2244 [JDG] Broken backward compatibility after moving to SPLIT_DATA env var

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

        Bug - A problem that impairs or prevents the functions of the product. CLOUD-2242 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.
        • Closed
        is documented by

        Bug - A problem that impairs or prevents the functions of the product. CLOUD-2239 [EAP] Check that A-MQ resources are recovered 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.
        • New

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

        Bug - A problem that impairs or prevents the functions of the product. CLOUD-2248 Transaction recovery in migration pod sometimes doesn't remove orphans

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

        Bug - A problem that impairs or prevents the functions of the product. CLOUD-2236 [EAP] Verify clean pod termination on scale down for tx recovery

        • 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

        Bug - A problem that impairs or prevents the functions of the product. CLOUD-2261 [EAP][XA][Recovery][NFS] split lock is broken after a minute of network partition

        • 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

        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-2223 EAP Transaction subsystem JDBC store tables should be prefixed with the node name

        • 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

            kconner@redhat.com Kevin Conner (Inactive)
            kconner@redhat.com Kevin Conner (Inactive)
            Marek Schmidt Marek Schmidt
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: