New Replication Storage Layer ❏ Replication Task Flow ❏ Revisit Serial Replication Abstract ❏ New Replication Storage Layer ❏ Replication Task Flow ❏ Revisit Serial Replication Problems of original Replication Tools Abstract ❏ New Replication Storage Layer ❏ Replication Task Flow ❏ Revisit Serial Replication Replication task flow - version #0 HMaster Region Server - 0 Client 1.Add Peer Request ZK not alive. (HBASE-12769) ○ Hard to implement the more complex task flow for Serial Replication & Sync Replication) Replication task flow - version #1 HMaster Region Server - 0 Client 1.Add Peer Request

write for TiFlash • TiKV introduces a new flow control mechanism to replace the previous RocksDB write stall mechanism to improve the stability of TiKV flow control • Simplify the operation and maintenance default value is 8192. TiKV con- figuration file storage. �→ flow- �→ control �→ .enable Newly added Determines whether to enable the flow control mechanism. The default value is true. 33 Configuration con- figuration file storage. �→ flow- �→ control �→ . �→ memtables �→ - �→ threshold �→ Newly added When the number of kvDB memtables reaches this threshold, the flow control mechanism starts to work

least privileges on TiDB Dashboard to enhance system security • Optimize the timestamp processing flow in TiDB to improve the overall performance • Enhance the performance of TiDB Data Migration (DM) so User document 2.2.2.3 Performance • Optimize the timestamp processing flow of PD TiDB optimizes its timestamp processing flow and reduces the timestamp processing load of PD by enabling PD Follower service, you can execute Drop/Truncate �→ Table or scale out the nodes. – Simplify the algorithm of L0 flow control #10879 – Improve the error log report in the raft client module #10944 – Improve logging

policies for low priority tasks. TiKV ensures that higher priority tasks are executed first by adding flow control to low priority tasks. PD cert- �→ allowed �→ -cn Modified Starting from v8.4.0, configur- when handling a large number of DELETE versions #17269 @AndreMouche • Support dynamically modifying flow-control configurations for write operations #17395 @glorv • Improve the speed of Region Merge in Y Y Y Y Y Y Y Y JSON type Y Y Y Y Y Y Y E E E E E Vectort types E N N N N N N N N N N N Control flow functions Y Y Y Y Y Y Y Y Y Y Y Y String functions Y Y Y Y Y Y Y Y Y Y Y Y Numeric functions and

policies for low priority tasks. TiKV ensures that higher priority tasks are executed first by adding flow control to low priority tasks. PD cert- �→ allowed �→ -cn Modified Starting from v8.4.0, configur- when handling a large number of DELETE versions #17269 @AndreMouche • Support dynamically modifying flow-control configurations for write operations #17395 @glorv • Improve the speed of Region Merge in Y Y Y Y Y Y Y Y JSON type Y Y Y Y Y Y Y E E E E E Vectort types E N N N N N N N N N N N Control flow functions Y Y Y Y Y Y Y Y Y Y Y Y String functions Y Y Y Y Y Y Y Y Y Y Y Y Numeric functions and

types Y Y Y Y Y Y Y Y Y Y String types Y Y Y Y Y Y Y Y Y Y JSON type Y Y Y E E E E E E E Control flow functions Y Y Y Y Y Y Y Y Y Y String functions Y Y Y Y Y Y Y Y Y Y Numeric functions and operators Create a flow Navigate to Amazon AppFlow > Flows and click Create flow. Figure 73: create flow 4.13.4.3.1 Set the flow name Enter the flow name, and then click Next. 584 Figure 74: name flow 4.13.4 Figure 82: complete flow 8. In the Error handling area, choose Stop the current flow run. In the Flow trigger area, choose the Run on demand trigger type, which means you need to run the flow manually. Then

the disk ca- pacity is full #11224 • PD – Fix the issue that Region statistics are not affected by flow-round-by-digit #4295 – Fix the issue that the scheduling operator cannot fail fast because the target JSON type Experimental Experimental Experimental Experimental Experimental Experimental Control flow functions Y Y Y Y Y Y String functions Y Y Y Y Y Y Numeric functions and operators Y Y Y Y Y Y the backoff time. For more details, refer to 4.3. TiKV server is busy is a result of the internal flow control mechanism and should not be counted in the backoff time. This issue will be fixed. 493 •

Experimental Experimental Experimental Experimental Experimental Experimental Experimental Control flow functions Y Y Y Y Y Y Y Y String functions Y Y Y Y Y Y Y Y Numeric functions and operators Y Y Create a flow Navigate to Amazon AppFlow > Flows and click Create flow. Figure 30: create flow 4.13.4.3.1 Set the flow name Enter the flow name, and then click Next. 520 Figure 31: name flow 4.13.4 Figure 39: complete flow 8. In the Error handling area, choose Stop the current flow run. In the Flow trigger area, choose the Run on demand trigger type, which means you need to run the flow manually. Then

Y Y Y Y Y Y Y Y Y Y String types Y Y Y Y Y Y Y Y Y Y Y JSON type Y Y Y Y E E E E E E E Control flow functions Y Y Y Y Y Y Y Y Y Y Y String functions Y Y Y Y Y Y Y Y Y Y Y Numeric functions and operators Create a flow Navigate to Amazon AppFlow > Flows and click Create flow. Figure 73: create flow 4.13.4.3.1 Set the flow name Enter the flow name, and then click Next. 597 Figure 74: name flow 4.13.4 Figure 82: complete flow 8. In the Error handling area, choose Stop the current flow run. In the Flow trigger area, choose the Run on demand trigger type, which means you need to run the flow manually. Then

your TiFlash cluster. • On the CDC panels, you can easily view the health, replication latency, data flow, and downstream write latency of your TiCDC cluster. For more information, see documentation. 2 migrating incremental data from upstream to downstream databases, there is a small probability that data flow might cause errors or data loss. In scenarios where strong data consistency is required, such as credit Date and time types Y Y Y Y Y Y Y Y String types Y Y Y Y Y Y Y Y JSON type Y E E E E E E E Control flow functions Y Y Y Y Y Y Y Y String functions Y Y Y Y Y Y Y Y Numeric functions and operators Y Y Y