- 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
- Azure Blob 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.3
- v1.2
- v1.1
- v1.0
- v0
TiDB Operator 1.2.0 Release Notes
Release date: July 29, 2021
TiDB Operator version: 1.2.0
Rolling update changes
- Upgrading TiDB Operator will cause the recreation of the TidbMonitor Pod due to #4085
New features
- Support setting Prometheus
retentionTime
, which is more fine-grained thanreserveDays
, and onlyretentionTime
takes effect if both are configured (#4085, @better0332) - Support setting
priorityClassName
in theBackup
CR to specify the priority of the backup job (#4078, @mikechengwei)
Improvements
- Changes the default Region leader eviction timeout of TiKV to 1500 minutes. The change prevents the Pod from being deleted when the Region leaders are not transferred completely to the other stores, which will cause data corruption (#4071, @KanShiori)
Bug fixes
- Fix the issue that the URL in
Prometheus.RemoteWrite
may be parsed incorrectly inTiDBMonitor
(#4087, @better0332)
Was this page helpful?