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

Monitor progress of ALTER TABLE ... ADD INDEX, ALGORITHM=INPLACE for InnoDB

    Details

    • Type: Task
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Fix Version/s: 10.1.1
    • Component/s: None
    • Labels:
      None

      Description

      When adding an index to an InnoDB table using algorithm=inplace, it is not possible to monitor the progress of the merge sort operation, which can take a great deal of time.

      It would be nice if the "Progress" column of SHOW PROCESSLIST was updated with some information about how far along the merge sort has progressed. It might also be possible or desirable to make some progress information available by other means.

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            jplindst Jan Lindström added a comment -

            commit 8984bef2e431db42761d3f267b950293cfd864de
            Author: Jan Lindström <jan.lindstrom@skysql.com>
            Date: Mon Aug 18 10:52:59 2014 +0300

            MDEV-6172: Monitor progress of ALTER TABLE ... ADD INDEX,
            ALGORITHM=INPLACE for InnoDB

            Added thd_progress calls to row_merge_sort to give
            some hint how merge sort progresses.

            Show
            jplindst Jan Lindström added a comment - commit 8984bef2e431db42761d3f267b950293cfd864de Author: Jan Lindström <jan.lindstrom@skysql.com> Date: Mon Aug 18 10:52:59 2014 +0300 MDEV-6172 : Monitor progress of ALTER TABLE ... ADD INDEX, ALGORITHM=INPLACE for InnoDB Added thd_progress calls to row_merge_sort to give some hint how merge sort progresses.

              People

              • Assignee:
                jplindst Jan Lindström
                Reporter:
                kolbe Kolbe Kegel
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 2 hours
                  2h