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

Transaction recovery in migration pod sometimes doesn't remove orphans

    Details

      Description

      We are running multiple test iterations of test doing "ungraceful" shutdown and scaling down a pod. The test is using 3 byteman rules to sleep for 3 seconds during transaction processing (AT EXIT prepare, AT ENTRY commit, AT EXIT commit).
      The EAP is correctly started in migration pod every time and the data are consistent in the databases. The problem is that sometimes there are remaining records in pg_prepared_xacts after recovery finished successfully.

      See the attached logs. In case of iteration_0_-xa-load-migration-1-g97ds there were remaining records in the table opposite to iteration_2_-xa-load-migration-1-tfdqd when it was correctly cleaned up.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  kconner Kevin Conner
                  Reporter:
                  tremes Tomas Remes
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  7 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: