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

Replication Lagging Way Behind On 5.5.1

Details

    • Bug
    • Status: Closed (View Workflow)
    • Blocker
    • Resolution: Duplicate
    • 5.5.1
    • 5.5.2
    • N/A
    • None
    • Centos 8

    Description

      Binlog replication is falling way behind on a 3 node MariaDB async cluster with Columnstore engine activated.

      io_thread is fine. sql_thread is stuck on a columnstore query on slaves/replicas.

      columnstore_replication_slave = OFF

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. MCOL-4515 Binlog replication getting stuck when running insert into <CS table> select .. from <CS table>

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            toddstoffel Todd Stoffel (Inactive) created issue -
            toddstoffel Todd Stoffel (Inactive) made changes -
            Field Original Value New Value
            Component/s N/A [ 15201 ]
            Resolution Duplicate [ 3 ]
            Status Open [ 1 ] Closed [ 6 ]
            toddstoffel Todd Stoffel (Inactive) made changes -
            toddstoffel Todd Stoffel (Inactive) made changes -
            Fix Version/s 5.5.2 [ 25601 ]
            Fix Version/s 5.6.1 [ 25031 ]
            mariadb-jira-automation Jira Automation (IT) made changes -
            Zendesk Related Tickets 196982

            People

              Unassigned Unassigned
              toddstoffel Todd Stoffel (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 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.