Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-5293

Replication not working after failover -restart pm1

Details

    • Bug
    • Status: Closed (View Workflow)
    • Blocker
    • Resolution: Fixed
    • None
    • 22.08.7
    • cmapi
    • 2022-22

    Description

      Build tested: 22.08.2, latest build from drone (#5838)

      Steps:

      1. Create a 3PM docker cluster
      2. Check cluster status on PM1. master=PM1, slave=PM2, PM3
      3. Create a database and a table, insert a row in PM1
      4. Verify table gets replicated to PM2
      5. Execute "docker container stop mcs1", wait 90 seconds
      6. Execute "docker container start mcs1", wait 60 seconds
      7. Check cluster status on PM1. master=PM1, slave=PM2, PM3
      Yesterday, I noticed MaxScale had PM2 sat as the master
      Today, MaxScale also set PM1 as the master (I don't know why such behavior today)

      For this test, PM2 was expected to take over as the master

      8. Create another table and inserted a row on PM1
      9. The table did not get replicated to PM2 or PM3
      10. "show slave status" on PM2 returned nothing
      11. "show slave status" on PM3 did return status, and no error

      PM3 slave status showed master log mariadb-bin.000002, position 4684
      PM1 master status showed master log mariadb-bin.000004, position 568

      Attachments

        Issue Links

          Activity

            drrtuy Roman added a comment -

            The scenario David.Hall mentioned should be re-tested when MCOL-5306 is tested.

            drrtuy Roman added a comment - The scenario David.Hall mentioned should be re-tested when MCOL-5306 is tested.

            Build verified: 22.08.7

            engine: e243a5332b8613ce0e370a503461990fefc24fce
            server: d3049350bb5c61340f5a7518b155d3c9dacdcb33
            buildNo: 6202

            Executed test case in mustest, test advance.a000_failover.test

            Steps performed.

             	echo Checking MaxScale status......
                echo Checking ColumnStore status on mcs1......
                echo Running sanity test on mcs1......
                echo Checking ColumnStore status on mcs1......
                echo Stopping node mcs1......
             	echo Checking MaxScale status......
                echo Checking ColumnStore status on mcs2......
                echo Starting node mcs1......
                echo Checking MaxScale status......
                echo Checking ColumnStore status on mcs1......
                echo Create a 1g DBT2 database on mcs2......
                echo Check row counts on mcs1 for replication......
                echo Drop test database......
                echo Ending of test.
            

            Test result, output from the test, has been attached.

            dleeyh Daniel Lee (Inactive) added a comment - Build verified: 22.08.7 engine: e243a5332b8613ce0e370a503461990fefc24fce server: d3049350bb5c61340f5a7518b155d3c9dacdcb33 buildNo: 6202 Executed test case in mustest, test advance.a000_failover.test Steps performed. echo Checking MaxScale status...... echo Checking ColumnStore status on mcs1...... echo Running sanity test on mcs1...... echo Checking ColumnStore status on mcs1...... echo Stopping node mcs1...... echo Checking MaxScale status...... echo Checking ColumnStore status on mcs2...... echo Starting node mcs1...... echo Checking MaxScale status...... echo Checking ColumnStore status on mcs1...... echo Create a 1g DBT2 database on mcs2...... echo Check row counts on mcs1 for replication...... echo Drop test database...... echo Ending of test. Test result, output from the test, has been attached.

            People

              drrtuy Roman
              dleeyh Daniel Lee (Inactive)
              Daniel Lee Daniel Lee (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.