-
Bug
-
Resolution: Done
-
Blocker
-
None
-
CLOUD Maintenance Sprint 21
When a network partition separates an NFS persistent volume from a particular EAP pod, the split lock becomes available, thus the migration pod starts an eap recovery on such split. This may cause multiple EAP processes writing to the same split directory if the partition ends at that time
Finished Migration Check cycle, pausing for 30 seconds before resuming Finished Migration Check cycle, pausing for 30 seconds before resuming Process has terminated abnorminally, forcing a termination check Attempting to migrate directory: (/opt/eap/standalone/partitioned_data/split-1) Waiting for grace period to expire, remaining timeout is 29 seconds Attempting to obtain lock for directory: (/opt/eap/standalone/partitioned_data/split-1) Successfully locked directory: (/opt/eap/standalone/partitioned_data/split-1)
- incorporates
-
CLOUD-2942 EAP CD 14 Release
- Closed
- is incorporated by
-
CLOUD-3088 EAP64 - Release EAP 6.4 - 1.9.0
- Closed
- is related to
-
CLOUD-2760 [EAP][XA] jta-crash-rec-eap7 quickstart doesn't work with sprint-21 img
- New
-
CLOUD-2210 [EAP] Support transaction recovery on scaling down of pods
- Verified
-
CLOUD-2770 CLOUD-2261 fix is missing in EAP CD and EAP 7.2 branches
- Verified
-
CLOUD-2761 [EAP][Recovery] Migration pod starts with permission errors in log
- Closed
-
CLOUD-2542 [EAP][XA][Recovery] Running transaction recovery in environment where shared persistent volume is not available
- Verified
- relates to
-
CLOUD-2767 [EAP][XA] EAP in migration pod hangs during shutdown on GlusterFS
- Verified
-
CLOUD-2486 Instability of xpaas-qe test PostgreSQLXARecoveryWithNFSDisconnectLoadTest
- Closed
-
CLOUD-2519 Enhancing the transaction crash recovery tests with failures on resource managers availability after scale down
- New