pingcap/tiflow

Optimization for DDL execution

Offen

#866 geöffnet am 20.08.2020

 (1 Kommentar) (0 Reaktionen) (1 zugewiesene Person)Go (310 Forks)auto 404
component/replica-modelcomponent/sinkhelp wanted

Repository-Metriken

Stars
 (461 Sterne)
PR-Merge-Metriken
 (PR-Metriken ausstehend)

Beschreibung

Feature Request

Is your feature request related to a problem? Please describe:

In the current replication model, DDL is executed synchronously and blocks all DMLs in other tables. This could cause replication block in some scenarios

  • the DDL is slow, such add index to a large table.
  • the replication of one table is slow, other tables will have to wait for this table catch up because the DDL is a strong barrier.

Describe the feature you'd like:

  • Currently DDL execution has no timeout, should we add some restriction. https://github.com/pingcap/ticdc/pull/936
  • Once the add index command has been sent to TiDB, even the client is timeout, we can ignore this error and continue replication.
  • Could we add some mechanism to allow single table DDL doesn't block DML replication of other tables.

Contributor Guide