TiDB 2.1 GA Release Notes
On November 30, 2018, TiDB 2.1 GA is released. See the following updates in this release. Compared with TiDB 2.0, this release has great improvements in stability, performance, compatibility, and usability.
TiDB
SQL Optimizer
Optimize the selection range of
Index Jointo improve the execution performanceOptimize the selection of outer table for
Index Joinand use the table with smaller estimated value of Row Count the as the outer tableOptimize Join Hint
TIDB_SMJso that Merge Join can be used even without proper index availableOptimize Join Hint
TIDB_INLJto specify the Inner table to JoinOptimize correlated subquery, push down Filter, and extend the index selection range, to improve the efficiency of some queries by orders of magnitude
Support using Index Hint and Join Hint in the
UPDATEandDELETEstatementSupport pushing down more functions:
ABS/CEIL/FLOOR/IS TRUE/IS FALSEOptimize the constant folding algorithm for the
IFandIFNULLbuilt-in functionsOptimize the output of the
EXPLAINstatement and use hierarchy structure to show the relationship between operators
SQL executor
Refactor all the aggregation functions and improve execution efficiency of the
StreamandHashaggregation operatorsImplement the parallel
Hash Aggregateoperators and improve the computing performance by 350% in some scenariosImplement the parallel
Projectoperators and improve the performance by 74% in some scenariosRead the data of the Inner table and Outer table of
Hash Joinconcurrently to improve the execution performanceOptimize the execution speed of the
REPLACE INTOstatement and increase the performance nearly by 10 timesOptimize the memory usage of the time data type and decrease the memory usage of the time data type by fifty percent
Optimize the point select performance and improve the point select efficiency result of Sysbench by 60%
Improve the performance of TiDB on inserting or updating wide tables by 20 times
Support configuring the memory upper limit of a single statement in the configuration file
Optimize the execution of Hash Join, if the Join type is Inner Join or Semi Join and the inner table is empty, return the result without reading data from the outer table
Support using the
EXPLAIN ANALYZEstatement to check the runtime statistics including the execution time and the number of returned rows of each operator
Statistics
Support enabling auto ANALYZE statistics only during certain period of the day
Support updating the table statistics automatically according to the feedback of the queries
Support configuring the number of buckets in the histogram using the
ANALYZE TABLE WITH BUCKETSstatementOptimize the Row Count estimation algorithm using histogram for mixed queries of equality query and range queries
Expressions
Support following built-in function:
json_containsjson_contains_pathencode/decode
Server
Support queuing the locally conflicted transactions within tidb-server instance to optimize the performance of conflicted transactions
Support Server Side Cursor
Add the HTTP API
Scatter the distribution of table Regions in the TiKV cluster
Control whether to open the
general logSupport modifying the log level online
Check the TiDB cluster information
Add the
auto_analyze_ratiosystem variables to contorl the ratio of AnalyzeAdd the
tidb_retry_limitsystem variable to control the automatic retry times of transactionsSupport using
admin show slowstatement to obtain the slow queriesAdd the
tidb_slow_log_thresholdenvironment variable to set the threshold of slow log automatically
DDL
Support the parallel execution of the Add index statement and other statements to avoid the time consuming Add index operation blocking other operations
Optimize the execution speed of
ADD INDEXand improve it greatly in some scenariosSupport the
select tidb_is_ddl_owner()statement to facilitate deciding whether TiDB isDDL OwnerSupport the
ALTER TABLE FORCEsyntaxSupport the
ALTER TABLE RENAME KEY TOsyntaxAdd the table name and database name in the output information of
admin show ddl jobs
Compatibility
Support more MySQL syntaxes
Make the
BITaggregate function support theALLparameterSupport the
SHOW PRIVILEGESstatementSupport the
CHARACTER SETsyntax in theLOAD DATAstatementSupport the
IDENTIFIED WITHsyntax in theCREATE USERstatementSupport the
LOAD DATA IGNORE LINESstatementThe
Show ProcessListstatement returns more accurate information
Placement Driver (PD)
Optimize availability
Introduce the version control mechanism and support rolling update of the cluster compatibly
Enable
Raft PreVoteamong PD nodes to avoid leader reelection when network recovers after network isolationEnable
raft learnerby default to lower the risk of unavailable data caused by machine failure during schedulingTSO allocation is no longer affected by the system clock going backwards
Support the
Region mergefeature to reduce the overhead brought by metadata
Optimize the scheduler
Optimize the processing of Down Store to speed up making up replicas
Optimize the hotspot scheduler to improve its adaptability when traffic statistics information jitters
Optimize the start of Coordinator to reduce the unnecessary scheduling caused by restarting PD
Optimize the issue that Balance Scheduler schedules small Regions frequently
Optimize Region merge to consider the number of rows within the Region
Improve PD simulator to simulate the scheduling scenarios
API and operation tools
Add the
GetPrevRegioninterface to support theTiDB reverse scanfeatureAdd the
BatchSplitRegioninterface to speed up TiKV Region splittingAdd the
GCSafePointinterface to support distributed GC in TiDBAdd the
GetAllStoresinterface, to support distributed GC in TiDB
pd-ctl supports:
- pd-recover doesn't need to provide the
max-replicaparameter
Metrics
Add related metrics for
FilterAdd metrics about etcd Raft state machine
Performance
Optimize the performance of Region heartbeat to reduce the memory overhead brought by heartbeats
Optimize the Region tree performance
Optimize the performance of computing hotspot statistics
TiKV
Coprocessor
Add more built-in functions
Add Coprocessor
ReadPoolto improve the concurrency in processing the requestsFix the time function parsing issue and the time zone related issues
Optimize the memory usage for pushdown aggregation computing
Transaction
Optimize the read logic and memory usage of MVCC to improve the performance of the scan operation and the performance of full table scan is 1 time better than that in TiDB 2.0
Fold the continuous Rollback records to ensure the read performance
Add the
UnsafeDestroyRangeAPI to support to collecting space for the dropping table/indexSeparate the GC module to reduce the impact on write
Add the
upper boundsupport in thekv_scancommand
Raftstore
Improve the snapshot writing process to avoid RocksDB stall
Add the
LocalReaderthread to process read requests and reduce the delay for read requestsSupport
BatchSplitto avoid large Region brought by large amounts of writeSupport
Region Splitaccording to statistics to reduce the I/O overheadSupport
Region Splitaccording to the number of keys to improve the concurrency of index scanImprove the Raft message process to avoid unnecessary delay brought by
Region SplitEnable the
PreVotefeature by default to reduce the impact of network isolation on services
Storage Engine
Fix the
CompactFilesbug in RocksDB and reduce the impact on importing data using LightningUpgrade RocksDB to v5.15 to fix the possible issue of snapshot file corruption
Improve
IngestExternalFileto avoid the issue that flush could block write
tikv-ctl
The
compactcommand supports specifying whether to compact data in the bottommost level
Tools
Fast full import of large amounts of data: TiDB Lightning
Support new TiDB Binlog
Upgrade caveat
- TiDB 2.1 does not support downgrading to v2.0.x or earlier due to the adoption of the new storage engine
Parallel DDL is enabled in TiDB 2.1, so the clusters with TiDB version earlier than 2.0.1 cannot upgrade to 2.1 using rolling update. You can choose either of the following two options:
- Stop the cluster and upgrade to 2.1 directly
- Roll update to 2.0.1 or later 2.0.x versions, and then roll update to the 2.1 version
- If you upgrade from TiDB 2.0.6 or earlier to TiDB 2.1, check if there is any ongoing DDL operation, especially the time consuming
Add Indexoperation, because the DDL operations slow down the upgrading process. If there is ongoing DDL operation, wait for the DDL operation finishes and then roll update.