- Introduction
- Get Started
- Deploy
- In Self-Managed Kubernetes
- In Public Cloud Kubernetes
- Deploy TiDB on ARM64 Machines
- Deploy TiFlash to Explore TiDB HTAP
- Deploy TiDB Across Multiple Kubernetes Clusters
- Deploy a Heterogeneous TiDB Cluster
- Deploy TiCDC
- Deploy TiDB Binlog
- Monitor and Alert
- Migrate
- Import Data
- Migrate from MySQL
- Migrate TiDB to Kubernetes
- Manage
- Secure
- Scale
- Upgrade
- Upgrade a TiDB Cluster
- Upgrade TiDB Operator
- Backup and Restore
- Overview
- Backup and Restore Custom Resources
- Grant Permissions to Remote Storage
- Amazon S3 Compatible Storage
- Google Cloud Storage
- Persistent Volumes
- Maintain
- Restart a TiDB Cluster
- Destroy a TiDB Cluster
- View TiDB Logs
- Modify TiDB Cluster Configuration
- Configure Automatic Failover
- Pause Sync of TiDB Cluster
- Maintain Different TiDB Clusters Separately Using Multiple TiDB Operator
- Maintain Kubernetes Nodes
- Migrate from Helm 2 to Helm 3
- Replace Nodes for a TiDB Cluster
- Disaster Recovery
- Troubleshoot
- FAQs
- Reference
- Release Notes
- v1.2
- v1.1
- v1.0
- v0
TiDB Operator 1.1.6 Release Notes
Release date: October 16, 2020
TiDB Operator version: 1.1.6
Compatibility Changes
With #3342, the
spec.pd.config
will be migrated from YAML format to TOML format automatically; however, if the following parameters are configured in thespec.pd.config
, the migration cannot be done after upgrading TiDB Operator to v1.1.6. Therefore, please edit theTidbCluster
CR to change the value of the parameter from string format to bool format, for example, from"true"
totrue
.replication.strictly-match-label
replication.enable-placement-rules
schedule.disable-raft-learner
schedule.disable-remove-down-replica
schedule.disable-replace-offline-replica
schedule.disable-make-up-replica
schedule.disable-remove-extra-replica
schedule.disable-location-replacement
schedule.disable-namespace-relocation
schedule.enable-one-way-merge
schedule.enable-cross-table-merge
pd-server.use-region-storage
Rolling Update Changes
- If
tidb.pingcap.com/sysctl-init: "true"
is set forspec.tidb.annotations
orspec.tikv.annotations
, the TiDB or TiKV cluster will be rolling updated after upgrading TiDB Operator to v1.1.6 due to #3305. - If TiFlash is deployed, the TiFlash cluster will be rolling updated after upgrading TiDB Operator to v1.1.6 due to #3345.
New Features
- Add
spec.br.options
to the Backup and Restore CR to support customizing arguments for BR (#3360, @lichunzhu) - Add
spec.tikv.evictLeaderTimeout
to TidbCluster CR to make TiKV evict leader timeout configurable (#3344, @lichunzhu) - Support monitoring multiple TiDB clusters with one TidbMonitor CR when TLS is disabled.
spec.clusterScoped
is added to the TidbMonitor CR and needs to be set totrue
to monitor multiple clusters (#3308, @mikechengwei) - Support specifying resources for all initcontainers (#3305, @shonge)
- Support deploying heterogeneous TiDB clusters (#3003 #3009 #3113 #3155 #3253, @mikechengwei)
Improvements
- Support passing raw TOML config for TiFlash (#3355, @july2993)
- Support passing raw TOML config for TiKV/PD (#3342, @july2993)
- Support passing raw TOML config for TiDB (#3327, @july2993)
- Support passing raw TOML config for Pump (#3312, @july2993)
- Print proxy log of TiFlash to stdout (#3345, @lichunzhu)
- Add timestamp to the prefix of scheduled backup on GCS (#3340, @lichunzhu)
- Remove the apiserver and related packages (#3298, @lonng)
- Remove the PodRestarter controller and
tidb.pingcap.com/pod-defer-deleting
annotation (#3296, @lonng) - Use BR metadata to get the total backup size (#3274, @lichunzhu)
Bug Fixes
- Fix the problem that may bootstrap multiple PD clusters (#3365, @lichunzhu)
Was this page helpful?