您可以使用 性能模式 来监控 InnoDB 表的 ALTER TABLE 进度。You can monitor ALTER TABLE
progress for InnoDB tables using
Performance Schema.
有七个阶段事件,表示 ALTER TABLE 的不同阶段。每个阶段事件都报告了整体 ALTER TABLE 操作在其不同阶段的 WORK_COMPLETED 和 WORK_ESTIMATED 的累计值。WORK_ESTIMATED 是使用一个考虑了 ALTER TABLE 执行的所有工作量的公式计算出来的,并可能在 ALTER TABLE 处理过程中进行修正。WORK_COMPLETED 和 WORK_ESTIMATED 值是 ALTER TABLE 执行的所有工作的抽象表示。There are seven stage events that represent different phases of
ALTER TABLE. Each stage event
reports a running total of WORK_COMPLETED and
WORK_ESTIMATED for the overall
ALTER TABLE operation as it
progresses through its different phases.
WORK_ESTIMATED is calculated using a formula
that takes into account all of the work that
ALTER TABLE performs, and may be
revised during ALTER TABLE
processing. WORK_COMPLETED and
WORK_ESTIMATED values are an abstract
representation of all of the work performed by
ALTER TABLE.
按照发生顺序,ALTER TABLE 阶段事件包括:In order of occurrence, ALTER TABLE
stage events include:
stage/innodb/alter table (read PK and internal sort):当ALTER TABLE处于读取主键阶段时,该阶段处于活动状态。它以WORK_COMPLETED=0开始,并且WORK_ESTIMATED设置为主键中估计的页面数量。当该阶段完成时,WORK_ESTIMATED会更新为主键中的实际页面数量。stage/innodb/alter table (read PK and internal sort): This stage is active whenALTER TABLEis in the reading-primary-key phase. It starts withWORK_COMPLETED=0andWORK_ESTIMATEDset to the estimated number of pages in the primary key. When the stage is completed,WORK_ESTIMATEDis updated to the actual number of pages in the primary key.stage/innodb/alter table (merge sort):此阶段会针对每个由ALTER TABLE操作添加的索引重复执行。stage/innodb/alter table (merge sort): This stage is repeated for each index added by theALTER TABLEoperation.stage/innodb/alter table (insert):此阶段会针对每个由ALTER TABLE操作添加的索引重复执行。stage/innodb/alter table (insert): This stage is repeated for each index added by theALTER TABLEoperation.stage/innodb/alter table (log apply index):此阶段包括在运行ALTER TABLE时生成的 DML 日志的应用。stage/innodb/alter table (log apply index): This stage includes the application of DML log generated whileALTER TABLEwas running.stage/innodb/alter table (flush):在此阶段开始之前,WORK_ESTIMATED会根据刷新列表的长度更新为更准确的估计值。stage/innodb/alter table (flush): Before this stage begins,WORK_ESTIMATEDis updated with a more accurate estimate, based on the length of the flush list.stage/innodb/alter table (log apply table):此阶段包括应用在ALTER TABLE运行期间生成的并发 DML 日志。此阶段的持续时间取决于表更改的范围。如果表上没有运行并发 DML,则此阶段是瞬时的。stage/innodb/alter table (log apply table): This stage includes the application of concurrent DML log generated whileALTER TABLEwas running. The duration of this phase depends on the extent of table changes. This phase is instant if no concurrent DML was run on the table.stage/innodb/alter table (end):包括刷新阶段后出现的任何剩余工作,例如重新应用在ALTER TABLE运行期间在表上执行的 DML。stage/innodb/alter table (end): Includes any remaining work that appeared after the flush phase, such as reapplying DML that was executed on the table whileALTER TABLEwas running.
InnoDB ALTER
TABLE 阶段事件当前尚未考虑空间索引的添加。InnoDB ALTER
TABLE stage events do not currently account for the
addition of spatial indexes.
使用性能模式监控 ALTER TABLE 的示例ALTER TABLE Monitoring Example Using Performance Schema
下面的示例演示了如何启用 stage/innodb/alter table% 阶段事件工具和相关的消费者表来监控 ALTER TABLE 的进度。有关性能模式阶段事件工具和相关消费者的信息,请参阅第 29.12.5 节,“性能模式阶段事件表”。The following example demonstrates how to enable the
stage/innodb/alter table% stage event
instruments and related consumer tables to monitor
ALTER TABLE progress. For
information about Performance Schema stage event instruments and
related consumers, see
Section 29.12.5, “Performance Schema Stage Event Tables”.
启用
stage/innodb/alter%工具:Enable thestage/innodb/alter%instruments:mysql>
UPDATE performance_schema.setup_instrumentsSET ENABLED = 'YES'WHERE NAME LIKE 'stage/innodb/alter%';Query OK, 7 rows affected (0.00 sec) Rows matched: 7 Changed: 7 Warnings: 0启用阶段事件消费者表,其中包括
events_stages_current、events_stages_history和events_stages_history_long。Enable the stage event consumer tables, which includeevents_stages_current,events_stages_history, andevents_stages_history_long.mysql>
UPDATE performance_schema.setup_consumersSET ENABLED = 'YES'WHERE NAME LIKE '%stages%';Query OK, 3 rows affected (0.00 sec) Rows matched: 3 Changed: 3 Warnings: 0执行
ALTER TABLE操作。在本例中,在 employees 示例数据库的 employees 表中添加一个middle_name列。Run anALTER TABLEoperation. In this example, amiddle_namecolumn is added to the employees table of the employees sample database.mysql>
ALTER TABLE employees.employees ADD COLUMN middle_name varchar(14) AFTER first_name;Query OK, 0 rows affected (9.27 sec) Records: 0 Duplicates: 0 Warnings: 0通过查询性能模式
events_stages_current表来检查ALTER TABLE操作的进度。显示的阶段事件根据当前正在进行的ALTER TABLE阶段而有所不同。WORK_COMPLETED列显示已完成的工作量。WORK_ESTIMATED列提供剩余工作量的估计。Check the progress of theALTER TABLEoperation by querying the Performance Schemaevents_stages_currenttable. The stage event shown differs depending on whichALTER TABLEphase is currently in progress. TheWORK_COMPLETEDcolumn shows the work completed. TheWORK_ESTIMATEDcolumn provides an estimate of the remaining work.mysql>
SELECT EVENT_NAME, WORK_COMPLETED, WORK_ESTIMATEDFROM performance_schema.events_stages_current;+------------------------------------------------------+----------------+----------------+ | EVENT_NAME | WORK_COMPLETED | WORK_ESTIMATED | +------------------------------------------------------+----------------+----------------+ | stage/innodb/alter table (read PK and internal sort) | 280 | 1245 | +------------------------------------------------------+----------------+----------------+ 1 row in set (0.01 sec)events_stages_current表在ALTER TABLE操作完成后返回空集。在这种情况下,您可以检查events_stages_history表,以查看已完成操作的事件数据。例如:Theevents_stages_currenttable returns an empty set if theALTER TABLEoperation has completed. In this case, you can check theevents_stages_historytable to view event data for the completed operation. For example:mysql>
SELECT EVENT_NAME, WORK_COMPLETED, WORK_ESTIMATEDFROM performance_schema.events_stages_history;+------------------------------------------------------+----------------+----------------+ | EVENT_NAME | WORK_COMPLETED | WORK_ESTIMATED | +------------------------------------------------------+----------------+----------------+ | stage/innodb/alter table (read PK and internal sort) | 886 | 1213 | | stage/innodb/alter table (flush) | 1213 | 1213 | | stage/innodb/alter table (log apply table) | 1597 | 1597 | | stage/innodb/alter table (end) | 1597 | 1597 | | stage/innodb/alter table (log apply table) | 1981 | 1981 | +------------------------------------------------------+----------------+----------------+ 5 rows in set (0.00 sec)如上所示,
WORK_ESTIMATED的值在ALTER TABLE处理过程中进行了修改。初始阶段完成后的预计工作量为 1213。当ALTER TABLE处理完成时,WORK_ESTIMATED被设置为实际值,即 1981。As shown above, theWORK_ESTIMATEDvalue was revised duringALTER TABLEprocessing. The estimated work after completion of the initial stage is 1213. WhenALTER TABLEprocessing completed,WORK_ESTIMATEDwas set to the actual value, which is 1981.