pingcap / tidb-operator

TiDB operator creates and manages TiDB clusters running in Kubernetes.

https://docs.pingcap.com/tidb-in-kubernetes/

pingcap/tidb-operator Issues

TiDB-operator is unable to delete TiProxy servers
Updated 13 days ago2
TiDB-operator fails to start the tiproxy servers if spec.tiproxy.version not provided
Updated 13 days ago2
TiDB operator cannot scale up the tiflash after scaling down to 0
Updated 13 days ago2
Dependency Dashboard
Updated 13 days ago
Ensure pd leader is ready to serve when rolling update pd
Closed 19 days ago
If store number is 0, it is expected to set the volume backup to failed which will not blocked the whole clean schedule [restore for 5658]
Updated 25 days ago1
A TiKV was restarted before it was stopped for scheduling, and BR did not exit in a timely manner and set the status to failed, resulting in the cluster remaining in the pause schedule state [restore for 5583]
Updated 25 days ago1
tikv crash during volumerestore [restore for 5577]
Updated 25 days ago1
volumebackup will failed when there is more than 50 tags specified in snapshot [restore for 5540]
Updated 25 days ago1
volumebackup failed when backup restored cluster [restore for 5537]
Updated 25 days ago1
Stuck restore during data restore caused by stale peer [restore for 5531]
Updated 25 days ago1
If there is a PV with the same name (released status) in the namespace, it will cause the restore to fail [restore for 5505]
Updated 25 days ago1
volumebackup failed, error message is "init job deleted before all the volume snapshots are created" [restore for 5478]
Updated 25 days ago1
Pausing lighting will cause a loss of status when encountering a TikV restart, and backup needs to be set to fail [restore for 5442]
Updated 25 days ago1
TiKV failed for more than 5 minutes, and the system did not set the backup task as failed [restore for 5439]
Updated 25 days ago1
backup should be set to failed when error "failed to keep importing to store 17 being denied, the state might be inconsistency" occured [restore for 5437]
Updated 25 days ago1
When checking whether warmup has ended, if there are warmup jobs in other namespaces, it will interfere with the current results. [restore for 5405]
Updated 25 days ago1
volumeback failed. reason is "Pod backup-fed-ebs-tidb-operator-ebs-1-init-w5glk has failed, original reason " [restore for 5330]
Updated 25 days ago1
do volumebackup after scaling out cluster, backup failed [restore for 5306]
Updated 25 days ago1
delete restore data pod when restoring will cause restore progress stuck [restore for 5297]
Updated 25 days ago1
kill restore-data pod will cause restore failed [restore for 5295]
Updated 25 days ago1
TiKV failure last for 1 minute can cause backup failure [restore for 5294]
Updated 25 days ago1
When the restore data pod fails, the volumerestore task status is not set to failed [restore for 5293]
Updated 25 days ago1
it is recommended to check the number of tikv volumes when restoring [restore for 5287]
Updated 25 days ago1
volumerestore 时，operator 报错“sync failed, err: read backup meta from bucket qa-workload-datasets and prefix airbnb-ebs/rpod_loss_with_pdleader_10min-tidb-operator-ebs-2, err: blob (key "backupmeta") (code=Unknown)” [restore for 5284]
Updated 25 days ago1
The EBS backup task may cause the import task to fail [restore for 5282]
Updated 25 days ago1
backup job is stuck(snapshot is completed) [restore for 5281]
Updated 25 days ago1
there are 2 running volumebackup during volumebackupschedule [restore for 5271]
Updated 25 days ago1
for a 100T cluster after restore, the QPS decreased and became unstable in the first two hours [restore for 5269]
Updated 25 days ago1
az c snpshot backup takes a long time [restore for 5268]
Updated 25 days ago1
failure to access AWS during backup will cause the entire task to fail [restore for 5266]
Updated 25 days ago1
there is no complete time value in restore crd [restore for 5239]
Updated 25 days ago1
Kill warmup pod when do volume restore, warmup pod will not be restarted, which will cause restore failed [restore for 5235]
Updated 25 days ago1
backup status changed from failed to VolumeBackupComplete [restore for 5193]
Updated 25 days ago1
there is a error "MissingRegion: could not find region configuration" in volumerestore [restore for 5185]
Updated 25 days ago1
tikv gets stuck while syncing raft logs during volumerestore [restore for 5165]
Updated 25 days ago1
Need to add the restore name to the warmup job name, otherwise it will affect the next restore task [restore for 5160]
Updated 25 days ago1
The previous backup failed, which will affect the time for rerun the backup [restore for 5144]
Updated 25 days ago1
backup to be executed twice caused job failed [restore for 5143]
Updated 25 days ago1
When volumerestore to different numbers of tikv, it is recommended to use precheck to directly report an error [restore for 5129]
Updated 25 days ago1
When the backup commit ts of multiple k8s is inconsistent, it will cause the second phase of restore to be very slow [restore for 5109]
Updated 25 days ago1
Volume Restore failed [restore for 5090]
Updated 25 days ago1
Volume restore takes a long time [restore for 5089]
Updated 25 days ago1
Volume backup status should be displayed as Complete, with the first letter capitalized [restore for 5088]
Updated 25 days ago1
Deleting volume backup during its running can cause snapshot leakage [restore for 5087]
Updated 25 days ago1
One of the k8s backups failed, and the status of the entire task should be updated to failed [restore for 5086]
Updated 25 days ago1
The number of regions is much greater than the concurrent number of br, resulting in a particularly long volume restore time [restore for 5085]
Updated 25 days ago1
The GC safepoint exceeds resolved ts, causing the backup task to fail [restore for 5073]
Updated 25 days ago1
TiDB operator has invalid values in the examples they provided
Closed 2 months ago
TiDB operator does not delete original configmap after user changes the config in the cr, causing resource leak
Updated 2 months ago1