Skip to content

TiDB Operator v1.0.2
Compare
Choose a tag to compare
@weekface weekface released this 01 Nov 10:29
· 49 commits to release-1.0 since this release
v1.0.2
6e321f5
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

The AWS Terraform script uses auto-scaling-group for all components (PD/TiKV/TiDB/monitor). When an ec2 instance fails the health check, the instance will be replaced. This is helpful for those applications that are stateless or use EBS volumes to store data.

But a TiKV Pod uses instance store to store its data. When an instance is replaced, all the data on its store will be lost. TiKV has to resync all data to the newly added instance. Though TiDB is a distributed database and can work when a node fails, resyncing data can cost much if the dataset is large. Besides, the ec2 instance may be recovered to a healthy state by rebooting.

So we disabled the auto-scaling-group's replacing behavior in v1.0.2.

Auto-scaling-group scaling process can also be suspended according to its documentation if you are using v1.0.1 or prior versions.

Please check out CHANGELOG for a full list of changes. For user guide, please check out document.

Docker images:

docker pull pingcap/tidb-operator:v1.0.2
docker pull uhub.ucloud.cn/pingcap/tidb-operator:v1.0.2
Assets 11
Loading