TiKV - v5.4.1

Improvements

• Support displaying multiple Kubernetes clusters in the Grafana dashboard #12104

Bug Fixes

• Fix the issue that TiKV panics and destroys peers unexpectedly because the target Region to be merged is invalid #12232
• Fix a bug that stale messages cause TiKV to panic #12023
• Fix the issue of intermittent packet loss and out of memory (OOM) caused by the overflow of memory metrics #12160
• Fix the potential panic issue that occurs when TiKV performs profiling on Ubuntu 18.04 #9765
• Fix a bug that replica reads might violate the linearizability #12109
• Fix the TiKV panic issue that occurs when the target peer is replaced with the peer that is destroyed without being initialized when merging a Region #12048
• Fix a bug that TiKV might panic if it has been running for 2 years or more #11940
• Reduce the TiCDC recovery time by reducing the number of the Regions that require the Resolve Locks step #11993
• Fix the panic issue caused by deleting snapshot files when the peer status is Applying #11746
• Fix the issue that destroying a peer might cause high latency #10210
• Fix the panic issue caused by invalid assertion in resource metering #12234
• Fix the issue that slow score calculation is inaccurate in some corner cases #12254
• Fix the OOM issue caused by the resolved_ts module and add more metrics #12159
• Fix the issue that successfully committed optimistic transactions may report the Write Conflict error when the network is poor #34066
• Fix the TiKV panic issue that occurs when replica read is enabled on a poor network #12046