helping reduce the wait time for retriev- ing TS during the ex- ecution of queries in certain scenar- ios. 67 Variable name Change type Description 2.2.2.2 Configuration parameters Configuration file or Kafka messages to external storage. This feature is only ap- plicable to non- Open Protocol scenar- ios. 77 Configuration file or compo- nent Configuration parame- ter Change type Description TiDB Light- --wait-timeout 1200 [other options] Generally, a 20-minute waiting timeout is sufficient for most scenar- ios. For a more precise estimate, search for init stats info time in the TiDB log to get the statistics

helping reduce the wait time for retriev- ing TS during the ex- ecution of queries in certain scenar- ios. 62 Variable name Change type Description 2.2.2.2 Configuration parameters Configuration file or Kafka messages to external storage. This feature is only ap- plicable to non- Open Protocol scenar- ios. 72 Configuration file or compo- nent Configuration parame- ter Change type Description TiDB Light- --wait-timeout 1200 [other options] Generally, a 20-minute waiting timeout is sufficient for most scenar- ios. For a more precise estimate, search for init stats info time in the TiDB log to get the statistics

=" �→ coarse �→ - �→ grained �→ ". This ac- celerates restore speed in large- scale Region scenar- ios. TiCDC compression �→ Newly added Controls the behavior to compress redo log files. 62 Configuration them in advance. By running the same application with different JDBC configurations in these scenar- ios, this document shows you how the overall system performance is affected by different 1328 interactions cons are. Operators for accessing tables 1579 Operator Trigger Condi- tions Applicable Scenar- ios Explanations PointGet / Batch- PointGet When accessing tables in one or more single point ranges

--wait-timeout 1200 [other options] Generally, a 20-minute waiting timeout is sufficient for most scenar- ios. For a more precise estimate, search for init stats info time in the TiDB log to get the statistics them in advance. By running the same application with different JDBC configurations in these scenar- ios, this document shows you how the overall system performance is affected by different 1377 interactions cons are. Operators for accessing tables 1629 Operator Trigger Condi- tions Applicable Scenar- ios Explanations PointGet / Batch- PointGet When accessing tables in one or more single point ranges

--wait-timeout 1200 [other options] Generally, a 20-minute waiting timeout is sufficient for most scenar- ios. For a more precise estimate, search for init stats info time in the TiDB log to get the statistics them in advance. By running the same application with different JDBC configurations in these scenar- ios, this document shows you how the overall system performance is affected by different 1385 interactions cons are. Operators for accessing tables 1637 Operator Trigger Condi- tions Applicable Scenar- ios Explanations PointGet / Batch- PointGet When accessing tables in one or more single point ranges

--wait-timeout 1200 [other options] Generally, a 20-minute waiting timeout is sufficient for most scenar- ios. For a more precise estimate, search for init stats info time in the TiDB log to get the statistics them in advance. By running the same application with different JDBC configurations in these scenar- ios, this document shows you how the overall system performance is affected by different 1374 interactions cons are. Operators for accessing tables 1625 Operator Trigger Condi- tions Applicable Scenar- ios Explanations PointGet / Batch- PointGet When accessing tables in one or more single point ranges

problems in TiCDC. – Reduce the possibility of TiCDC replication interruption in the following scenar- ios: project#11 * Replication interruption when the network is unstable * Replication interruption when cons are. Operators for accessing tables 590 Operator Trigger Condi- tions Applicable Scenar- ios Explanations PointGet / Batch- PointGet When accessing tables in one or more single point ranges than calls the copro- cessor inter- face. 591 Operator Trigger Condi- tions Applicable Scenar- ios Explanations TableReaderNone Any scenario It is gener- ally con- sid- ered as the least effi- cient

--wait-timeout 1200 [other options] Generally, a 20-minute waiting timeout is sufficient for most scenar- ios. For a more precise estimate, search for init stats info time in the TiDB log to get the statistics them in advance. By running the same application with different JDBC configurations in these scenar- ios, this document shows you how the overall system performance is affected by different 1329 interactions cons are. Operators for accessing tables 1580 Operator Trigger Condi- tions Applicable Scenar- ios Explanations PointGet / Batch- PointGet When accessing tables in one or more single point ranges

--wait-timeout 1200 [other options] Generally, a 20-minute waiting timeout is sufficient for most scenar- ios. For a more precise estimate, search for init stats info time in the TiDB log to get the statistics them in advance. By running the same application with different JDBC configurations in these scenar- ios, this document shows you how the overall system performance is affected by different 1356 interactions cons are. Operators for accessing tables 1607 Operator Trigger Condi- tions Applicable Scenar- ios Explanations PointGet / Batch- PointGet When accessing tables in one or more single point ranges

--wait-timeout 1200 [other options] Generally, a 20-minute waiting timeout is sufficient for most scenar- ios. For a more precise estimate, search for init stats info time in the TiDB log to get the statistics them in advance. By running the same application with different JDBC configurations in these scenar- ios, this document shows you how the overall system performance is affected by different 1310 interactions cons are. Operators for accessing tables 1555 Operator Trigger Condi- tions Applicable Scenar- ios Explanations PointGet / Batch- PointGet When accessing tables in one or more single point ranges