TiKV - v5.1.5

Bug fixes

• Fix the issue of time parsing error that occurs when the DATETIME values contain a fraction and Z #12739
• Fix a bug that replica reads might violate the linearizability #12109
• Fix a bug that Regions might be overlapped if Raftstore is busy #13160
• Fix the TiKV panic issue that occurs when applying snapshot is aborted #11618
• Fix a bug that TiKV might panic if it has been running for 2 years or more #11940
• Fix the panic issue that might occur when the source peer catches up logs by snapshot in the Region merge process #12663
• Fix the issue that TiKV panics when performing type conversion for an empty string #12673
• Fix a bug that stale messages cause TiKV to panic #12023
• Fix the panic issue that might occur when a peer is being split and destroyed at the same time #12825
• 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 the issue that TiKV reports the invalid store ID 0 error when using Follower Read #12478
• Fix the possible duplicate commit records in pessimistic transactions when async commit is enabled #12615
• Support configuring the unreachable_backoff item to avoid Raftstore broadcasting too many messages after one peer becomes unreachable #13054
• Fix the issue that successfully committed optimistic transactions may report the Write Conflict error when the network is poor #34066
• Fix the wrong expression of Unified Read Pool CPU in dashboard #13086