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

Multi server upgrade ERROR in replication setup when table name contains 'failed'

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Trivial
    • Resolution: Won't Fix
    • 1.1.2
    • Icebox
    • installation
    • None
    • docker Ubuntu 16

    Description

      During multi-server system upgrade from InfiniDB 4.x to MariaDB ColumnStore 1.1.2 the postConfigure step

      Run MariaDB ColumnStore Replication Setup..
      

      fails with

      ERROR: Error return in running the MariaDB ColumnStore Master DB Distribute, check /tmp/master-dist*.logs on pm1
       
       MariaDB ColumnStore Replication Setup Failed, check logs
       
       IMPORTANT: Once issue has been resolved, rerun postConfigure
      

      The log file /tmp/master-dist_pm2.log has lines:

      sending incremental file list
      columnstore_info/db.opt
      ...
      user_analytics/failed_logins.frm
                 FAILED: Failure, check tmp log
      

      This issue is due to the lines like:

                 -re "failed" ...
      

      in the script
      https://github.com/mariadb-corporation/mariadb-columnstore-engine/blob/master/oam/install_scripts/rsync.sh#L47

      To fix this issue, one could add the --quiet option to the rsync command at:
      https://github.com/mariadb-corporation/mariadb-columnstore-engine/blob/master/oam/install_scripts/rsync.sh#L28

      set COMMAND "rsync -vopgrq ...
      

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              sasha Sasha V
              Votes:
              1 Vote for this issue
              Watchers:
              3 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.