TiDB 3.0.12 Release Notes
Release date: March 16, 2020
TiDB version: 3.0.12
TiDB Ansible version: 3.0.12
Compatibility Changes
- TiDB
- Fix the issue of inaccurate timing of prewrite binlog in slow query log. The original timing field was called
Binlog_prewrite_time
. After this fix, the name is changed toWait_prewrite_binlog_time
. #15276
- Fix the issue of inaccurate timing of prewrite binlog in slow query log. The original timing field was called
New Features
TiDB
- Support dynamic loading of the replaced certificate file by using the
alter instance
statement #15080 #15292 - Add the
cluster-verify-cn
configuration item. After configuration, the status service can only be used when with the corresponding CN certificate. #15164 - Add a flow limiting feature for DDL requests in each TiDB server to reduce the error reporting frequency of DDL request conflicts #15148
- Support exiting of the TiDB server when binlog write fails #15339
- Support dynamic loading of the replaced certificate file by using the
Tools
- TiDB Binlog
- Add the
kafka-client-id
configuration item in Drainer, which supports connecting to Kafka clients to configure the client ID #929
- Add the
- TiDB Binlog
Bug Fixes
TiDB
- Make
GRANT
,REVOKE
guarantee atomicity when modifying multiple users #15092 - Fix the issue that the locking of pessimistic lock on the partition table failed to lock the correct row #15114
- Make the error message display according to the value of
max-index-length
in the configuration when the index length exceeds the limit #15130 - Fix the incorrect decimal point issue of the
FROM_UNIXTIME
function #15270 - Fix the issue of conflict detection failure or data index inconsistency caused by deleting records written by oneself in a transaction #15176
- Make
TiKV
- Fix the issue of conflict detection failure or data index inconsistency caused by inserting an existing key into a transaction and then deleting it immediately when disabling the consistency check parameter #7054
- Introduce a flow control mechanism in Raftstore to solve the problem that without flow control, it might lead to too slow tracking and cause the cluster to be stuck, and the transaction size might cause frequent reconnection of TiKV connections #7072 #6993
PD
- Fix the issue of incorrect Region information caused by data race when PD processes Region heartbeats #2233
TiDB Ansible
- Support deploying multiple Grafana/Prometheus/Alertmanager in a cluster #1198