-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
EAP71 1.0.0.GA
-
None
-
Documentation (Ref Guide, User Guide, etc.)
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.
- documents
-
CLOUD-2210 [EAP] Support transaction recovery on scaling down of pods
- Verified
- is incorporated by
-
CLOUD-2243 Sprint 13 release
- Closed
- relates to
-
CLOUD-2238 Document the manual procedure for resolving in doubt transactions
- New