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

LDIF & cache_inserts - table lock stuck - unstable - crashes aria table on restart

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • None
    • 6.1.1
    • cache_insert
    • None
    • 2021-9, 2021-10, 2021-11, 2021-12

    Description

      When constantly loading data into CS with cache_inserts enabled via LDIF - The flush to CS freezes up, table locks and doesn't clear. Restarting Columnstore and MariaDB results in crashed aria tables. This is an unreliable process for clients needing to constantly load data.

      Desired Outcome: Table doesn't excessively lock and crash requiring mariadb restart and aria_chk.

      Steps to reproduce
      -----------------------------------------------------------
      deploy an aws t2.xlarge instance

      # Update yum and install CS
      yum update -y
      yum install wget -y
      wget https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup
      chmod +x mariadb_es_repo_setup
      ./mariadb_es_repo_setup --token="ca9d5fe2-ef44-438f-87ee-784ecc4fb9b0" --apply --mariadb-server-version="10.5" --mariadb-maxscale-version=2.5 
      yum -y install MariaDB-server
      systemctl start mariadb
      yum install MariaDB-columnstore-engine.x86_64 -y
       
      # add cache_inserts to config file
      vi /etc/my.cnf.d/server.cnf
      columnstore-cache-inserts=ON
       
      # Restart mariadb & CS
      systemctl restart mariadb
      systemctl restart mariadb-columnstore
       
       
      # Transfer the attached bash script & DDL & csv 
      cd /tmp/
      mariadb < DDL.sql
       
      # On window 1
      tail -f /var/log/messages
       
      # On window 2
      bash loadDataInfile.bash
       
      # Notice after 137 iterations notice the flush to CS takes FreqRatioEvenTrack[root@ip-172-31-5-47 tmp]# mariadb test -e "show processlist;"
      +-----+------+-----------+------+---------+------+------------+----------------------------------------------------------------------------------+----------+
      | Id  | User | Host      | db   | Command | Time | State      | Info                                                                             | Progress |
      +-----+------+-----------+------+---------+------+------------+----------------------------------------------------------------------------------+----------+
      | 148 | root | localhost | test | Query   |  667 | table lock | LOAD DATA INFILE '/tmp/test2.csv' INTO TABLE CCB_CI_SER FIELDS TERMINATED BY ',' |    0.000 |
      | 160 | root | localhost | NULL | Query   |    0 | starting   | show processlist                                                                 |    0.000 |
      +-----+------+-----------+------+---------+------+------------+----------------------------------------------------------------------------------+----------+
       
      # final message in /var/log/messages
      Jul  1 20:39:57 ip-172-31-5-47 env: ExeMgr[28955]: 57.624387 |2147483796|0|0| D 16 CAL0041: Start SQL statement: select objectid from systable where schema='test' and tablename='CCB_CI_SER' --tableRID/; ||
      Jul  1 20:39:57 ip-172-31-5-47 env: ExeMgr[28955]: 57.642600 |2147483796|0|0| D 16 CAL0042: End SQL statement
      

      Attachments

        1. DDL.sql
          3 kB
          Allen Herrera
        2. loadDataInfile.bash
          0.2 kB
          Allen Herrera
        3. test2.csv
          2.02 MB
          Allen Herrera

        Issue Links

          Activity

            People

              dleeyh Daniel Lee (Inactive)
              allen.herrera Allen Herrera
              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.