Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-8179

Absent progress report for operations on InnoDB tables

Details

    • 10.0.20

    Description

      See also MDEV-8178

      Initially mentioned on the mailing list: https://lists.launchpad.net/maria-discuss/msg02496.html

      Dataset: salaries table in the employees sample database.

      Examples of statements that show progress report on 5.5 and 10.1, but not on 10.0.

      ALTER TABLE salaries ENGINE = Innodb;
      		 
      ALTER TABLE salaries ADD id INT NULL;
      		 
      ALTER TABLE salaries DROP id;
      		 
      ALTER TABLE salaries ROW_FORMAT = COMPRESSED;

      It happened somewhere between 10.0.10 and 10.0.11.

      For MyISAM, progress is displayed.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-8471 No progress report for online DDL of InnoDB tables

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-29913 Assertion `thd->stmt_arena != thd->progress.arena' failed in thd_progress_init upon bulk load

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            elenst Elena Stepanova created issue -
            elenst Elena Stepanova made changes -
            Field Original Value New Value
            Status Open [ 1 ] Confirmed [ 10101 ]
            serg Sergei Golubchik made changes -
            Assignee Sergei Golubchik [ serg ] Jan Lindström [ jplindst ]
            serg Sergei Golubchik made changes -
            Sprint 10.0.20 [ 5 ]
            serg Sergei Golubchik made changes -
            Rank Ranked higher
            jplindst Jan Lindström (Inactive) made changes -
            Status Confirmed [ 10101 ] In Progress [ 3 ]
            jplindst Jan Lindström (Inactive) added a comment -

            In 5.5 you can see:

            MariaDB [employees]> ALTER TABLE salaries ENGINE = Innodb;
            		 
            --------------
            		 
            ALTER TABLE salaries ENGINE = Innodb
            		 
            --------------
            		 
             
            		 
            Stage: 1 of 2 'copy to tmp table'  0.808% of stage done

            On 10.0, there is no stage output at all.

            jplindst Jan Lindström (Inactive) added a comment - In 5.5 you can see: MariaDB [employees]> ALTER TABLE salaries ENGINE = Innodb; -------------- ALTER TABLE salaries ENGINE = Innodb --------------   Stage: 1 of 2 'copy to tmp table' 0.808% of stage done On 10.0, there is no stage output at all.
            jplindst Jan Lindström (Inactive) added a comment -

            There is regression between 10.0.10 and 10.0.11. In 10.0.10 ALTER TABLE salaries ENGINE = Innodb; client (e.g. mysql) does print stage output but on 10.0.11 client does not print any stage outputs. Rest of above statements do not print any stage outputs on 10.0.10. In 5.5 they do because 5.5 does not include on-line alter table. In 10.1 stage outputs are printed because MDEV-6172, commit 8984bef2e431db42761d3f267b950293cfd864de introduced a new feature where InnoDB/XtraDB sends a progress messages.

            jplindst Jan Lindström (Inactive) added a comment - There is regression between 10.0.10 and 10.0.11. In 10.0.10 ALTER TABLE salaries ENGINE = Innodb; client (e.g. mysql) does print stage output but on 10.0.11 client does not print any stage outputs. Rest of above statements do not print any stage outputs on 10.0.10. In 5.5 they do because 5.5 does not include on-line alter table. In 10.1 stage outputs are printed because MDEV-6172 , commit 8984bef2e431db42761d3f267b950293cfd864de introduced a new feature where InnoDB/XtraDB sends a progress messages.
            jplindst Jan Lindström (Inactive) made changes -
            Assignee Jan Lindström [ jplindst ] Sergei Golubchik [ serg ]
            Status In Progress [ 3 ] In Review [ 10002 ]
            jplindst Jan Lindström (Inactive) added a comment -

            I'l take this back. BUG# 13975227: ONLINE OPTIMIZE TABLE FOR INNODB TABLES, so we really should use online alter table also for alter table t1 engine=innodb. I will reconsider to merge progress info from 10.1 to 10.0.

            jplindst Jan Lindström (Inactive) added a comment - I'l take this back. BUG# 13975227: ONLINE OPTIMIZE TABLE FOR INNODB TABLES, so we really should use online alter table also for alter table t1 engine=innodb. I will reconsider to merge progress info from 10.1 to 10.0.
            jplindst Jan Lindström (Inactive) made changes -
            Assignee Sergei Golubchik [ serg ] Jan Lindström [ jplindst ]
            jplindst Jan Lindström (Inactive) made changes -
            Status In Review [ 10002 ] Stalled [ 10000 ]
            jplindst Jan Lindström (Inactive) made changes -
            Fix Version/s 10.0.20 [ 19201 ]
            Fix Version/s 10.0 [ 16000 ]
            Resolution Fixed [ 1 ]
            Status Stalled [ 10000 ] Closed [ 6 ]
            elenst Elena Stepanova made changes -
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 67561 ] MariaDB v4 [ 149184 ]
            marko Marko Mäkelä made changes -

            People

              jplindst Jan Lindström (Inactive)
              elenst Elena Stepanova
              Votes:
              1 Vote for this issue
              Watchers:
              4 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.