Agenda ● How to build a stable database ○ Schrodinger-test platform ○ Failpoint injection ○ Goroutine-leak detection ● Optimization ○ Chunk vs interface{} ○ Vectorized execution TiDB Overview TiDB TiDB TiDB goroutine leak What is goroutine leak? func main() { go func() { // Just invalid the deadlock detection. for { time.Sleep(1 * time.Second) } }() done := make(chan bool) leakCh := make(chan string, 1)

About Internode Communications (Gossip) 8 About Cluster Membership and Seed Nodes 9 About Failure Detection and Recovery 9 About Data Partitioning in Cassandra 10 About Partitioning in Multi-Data Center thrift_framed_transport_size_in_mb 75 thrift_max_message_length_in_mb 75 Internode Communication and Fault Detection Properties 75 dynamic_snitch 75 dynamic_snitch_badness_threshold 75 dynamic_snitch_reset_interval_in_ms tokens. About Failure Detection and Recovery Failure detection is a method for locally determining, from gossip state, if another node in the system is up or down. Failure detection information is also

vector search, similarity detection, and instant model updates for AI workloads. It can process data in a way that supports real-time, AI-driven insights (e.g., anomaly detection, predictions, and pattern integration: CrateDB enhances AI-driven applications by enabling real-time vector search, anomaly detection, and predictive insights—all with SQL simplicity. 85.4 Ready for AI CrateDB is a foundational

the conflict detection strategy for both logical and physical import modes via the conflict.strategy parameter. The duplicate-resolution parameter for the old version of conflict detection will be removed Rename scatter-range to scatter-range-scheduler in pd-ctl commands #8379 @okJiang • Add conflict detection for grant-hot-leader-scheduler #4903 @lhy1024 • TiFlash • Optimize the execution efficiency of in the source data. To let TiDB Lightning detect and resolve conflicting data, enable conflict detection. 6.3.6 Enable checkpoint For importing a large volume of data, it is essential to refer to Lightning

the conflict detection strategy for both logical and physical import modes via the conflict.strategy parameter. The duplicate-resolution parameter for the old version of conflict detection will be removed Rename scatter-range to scatter-range-scheduler in pd-ctl commands #8379 @okJiang • Add conflict detection for grant-hot-leader-scheduler #4903 @lhy1024 • TiFlash • Optimize the execution efficiency of in the source data. To let TiDB Lightning detect and resolve conflicting data, enable conflict detection. 6.3.6 Enable checkpoint For importing a large volume of data, it is essential to refer to Lightning

the conflict detection strategy for both logical and physical import modes via the conflict.strategy parameter. The duplicate-resolution parameter for the old version of conflict detection will be removed in the source data. To let TiDB Lightning detect and resolve conflicting data, enable conflict detection. 6.3.6 Enable checkpoint For importing a large volume of data, it is essential to refer to Lightning (instance)> 0 • Description: There is a slow TiKV node. raftstore.inspect-interval controls the detection of TiKV slow nodes. For more information, see raftstore.inspect-interval. • Solution: • Watch

the conflict detection strategy for both logical and physical import modes via the conflict.strategy parameter. The duplicate-resolution parameter for the old version of conflict detection will be removed in the source data. To let TiDB Lightning detect and resolve conflicting data, enable conflict detection. 6.3.6 Enable checkpoint For importing a large volume of data, it is essential to refer to Lightning (instance)> 0 • Description: There is a slow TiKV node. raftstore.inspect-interval controls the detection of TiKV slow nodes. For more information, see raftstore.inspect-interval. • Solution: • Watch

TiDB Lightning deprecates the old version of conflict detection strategy for the physical import mode, enables you to control the conflict detection strategy for both logical and physical import modes via import task. 54 • Starting from v8.0.0, TiDB Lightning deprecates the old version of conflict detection strategy for the physical import mode, and enables you to control the conflict detec- tion strategy in the source data. To let TiDB Lightning detect and resolve conflicting data, enable conflict detection. 6.3.6 Enable checkpoint For importing a large volume of data, it is essential to refer to Lightning

TiDB Lightning deprecates the old version of conflict detection strategy for the physical import mode, enables you to control the conflict detection strategy for both logical and physical import modes via TLSv1.2 or TLSv1.3. • Starting from v8.0.0, TiDB Lightning deprecates the old version of conflict detection strategy for the physical import mode, and enables you to control the conflict detec- tion strategy performance has been improved by up to 100 times. #50305 @ywqzzy • TiKV • Enhance TSO verification and detection to improve the robustness of the cluster TSO when the configuration or operation is improper #16545

TiDB Lightning deprecates the old version of conflict detection strategy for the physical import mode, enables you to control the conflict detection strategy for both logical and physical import modes via single import task. • Starting from v8.0.0, TiDB Lightning deprecates the old version of conflict detection strategy for the physical import mode, and enables you to control the conflict detec- tion strategy in the source data. To let TiDB Lightning detect and resolve conflicting data, enable conflict detection. 701 6.3.6 Enable checkpoint For importing a large volume of data, it is essential to refer to