title | summary |
---|---|
TiDB 8.5.1 Release Notes |
Learn about the operating system and platform requirement changes, improvements, and bug fixes in TiDB 8.5.1. |
Release date: January 17, 2025
TiDB version: 8.5.1
Quick access: Quick start | Production deployment
Starting from v8.5.1, TiDB resumes testing of CentOS Linux 7 and is compatible with it. If you plan to deploy TiDB v8.5 or upgrade your cluster to v8.5, ensure you use TiDB v8.5.1 or a later version.
-
TiDB v8.4.0 DMR and v8.5.0 releases dropped support and testing with CentOS Linux 7 because it reached EOL status on June 30, 2024. Upgrading a TiDB cluster on CentOS 7 to v8.4.0 or v8.5.0 will cause the risk of cluster unavailability.
-
To assist users still using CentOS Linux 7, TiDB resumes testing of CentOS Linux 7 starting from v8.5.1. However, due to the EOL status of CentOS Linux, it is strongly recommended that you review the official announcements and security guidance for CentOS Linux 7 and migrate to an operating system supported by TiDB for production use, such as Rocky Linux 9.1 or later.
As CentOS Linux 7 has reached EOL, testing of this distribution will be stopped in a future TiDB release.
-
TiDB
- Support folding read-only user-defined variables into constants #52742 @winoros
- Convert Cartesian product Semi Join with nulleq condition to Semi Join with equality condition #57583 @hawkingrei
- Adjust the default threshold of statistics memory cache to 20% of the total memory #58014 @hawkingrei
- Enhance the timestamp validity check #57786 @MyonKeminta
-
TiKV
-
TiFlash
-
Tools
-
TiDB
- Fix the issue that the default timeout for querying the TiFlash system table is too short #57816 @JaySon-Huang
- Fix the issue that when setting
tidb_gogc_tuner_max_value
andtidb_gogc_tuner_min_value
, if the maximum value is null, an incorrect warning message occurs #57889 @hawkingrei - Fix the issue that data indexes are inconsistent because plan cache uses the wrong schema when adding indexes #56733 @wjhuang2016
- Fix the issue that the data in the Stats Healthy Distribution panel of Grafana might be incorrect #57176 @hawkingrei
- Fix the issue that the last
ANALYZE
time of tables without collected statistics might not be NULL #57735 @winoros - Fix the issue that improper exception handling for statistics causes in-memory statistics to be mistakenly deleted when background tasks time out #57901 @hawkingrei
- Fix the issue that statistics are not cleared after executing the
DROP DATABASE
statement #57230 @Rustin170506 - Fix the issue that some predicates might be lost when constructing
IndexMerge
#58476 @hawkingrei - Fix the issue that creating a vector search index on a column with more than 3000 dimensions causes the
KeyTooLong
error #58836 @breezewish - Fix the issue that the
REORGANIZE PARTITION
operation does not correctly clean up replaced global indexes and handles unique indexes on non-clustered tables #56822 @mjonss - Fix the issue that the Range INTERVAL syntax sugar of partitioned tables does not support using
MINUTE
as the interval #57698 @mjonss - Fix the issue that changing the timezone causes incorrect query results when querying slow logs #58452 @lcwangchao
- Fix the issue that task cancellation failure might cause the task to leak when shrinking the TTL workers of scan tasks #57708 @YangKeao
- Fix the issue that after a heartbeat is lost and the TTL table is deleted or disabled, TTL jobs keep running #57702 @YangKeao
- Fix the issue that
last_job_finish_time
is displayed incorrectly after a TTL job is canceled #58109 @YangKeao - Fix the issue that TTL jobs cannot be canceled if the TiDB heartbeat is lost #57784 @YangKeao
- Fix the issue that a TTL job that loses the heartbeat blocks other jobs from getting heartbeats #57915 @YangKeao
- Fix the issue that when shrinking the TTL workers, some expired rows are not deleted #57990 @lcwangchao
- Fix the issue that the remaining rows are not retried when the TTL delete rate limiter is interrupted #58205 @lcwangchao
- Fix the issue that TTL might generate a large number of warning logs in certain cases #58305 @lcwangchao
- Fix the issue that some TTL jobs might hang when modifying
tidb_ttl_delete_rate_limit
#58484 @lcwangchao - Fix the issue that data backfill during
REORGANIZE PARTITION
might cause concurrent updates to be rolled back #58226 @mjonss - Fix the issue that using
ORDER BY
when queryingcluster_slow_query table
might generate unordered results #51723 @Defined2014
-
TiKV
- Fix the issue that encoding might fail when processing GBK/GB18030 encoded data #17618 @CbcWestwolf
- Fix the issue that TiKV panics due to uninitialized replicas when the TiKV MVCC In-Memory Engine (IME) preloads them #18046 @overvenus
- Fix the issue that the leader could not be quickly elected after Region split #17602 @LykxSassinator
- Fix the issue that TiKV cannot report heartbeats to PD when the disk is stuck #17939 @LykxSassinator
-
PD
-
TiFlash
- Fix the issue that querying new columns might return incorrect results under the disaggregated storage and compute architecture #9665 @zimulala
- Fix the issue that TiFlash might unexpectedly reject processing Raft messages when memory usage is low #9745 @CalvinNeo
- Fix the issue that the
POSITION()
function for TiFlash does not support character set collations #9377 @xzhangxian1008
-
Tools
-
Backup & Restore (BR)
-
TiCDC
- Fix the issue that the changefeed might get stuck after new TiKV nodes are added to the cluster #11766 @lidezhu
- Fix the issue that the event filter incorrectly uses the new table name instead of the old table name for filtering when processing
RENAME TABLE
DDL statements #11946 @kennytm - Fix the issue that goroutines leak occurs after a changefeed is deleted #11954 @hicqu
- Fix the issue that out-of-order messages resent by the Sarama client cause Kafka message order to be incorrect #11935 @3AceShowHand
- Fix the issue that the default value of the NOT NULL timestamp field in the Debezium protocol is incorrect #11966 @wk989898
-