pingcap / tidb-operator

TiDB operator creates and manages TiDB clusters running in Kubernetes.

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

Repository from Github https://github.compingcap/tidb-operator

pingcap/tidb-operator Issues

Dependency Dashboard
Updated 8 days ago
tidb Service resource is constantly being updated
Updated 8 days ago
backup with tikv: Table 'mysql.tidb' doesn't exist"
Updated 12 days ago
br: expose pod metrics to grafana
Updated 14 days ago
Invalid backup does not fail `VolumeBackup`
Closed 15 days ago
log backup: support log file flush during tikv graceful shutdown
Closed 19 days ago
TiDB does not work correctly on Ubuntu because pipefail is not available in dash.
Closed 21 days ago6
BackupSchedule: support automatic `backup log truncate` when only `maxBackups` is supplied
Updated a month ago
Backup spec.cleanPolicy: Delete does not fully delete objects in versioned S3 buckets
Updated a month ago
I would like to add allowPrivilegeEscalation
Updated a month ago7
PD crash loops during VolumeReplace due to bad member entry.
Updated 2 months ago1
Release v1.5.5
Closed 2 months ago
Extra namespace field will cause failure to create the cluster for the Quick Start tutorial
Closed 2 months ago1
Fail to resize Tikv PVCs
Updated 2 months ago3
TiDB Pods stay unhealthy after configuring the `port` parameter in TiDB configuration
Updated 3 months ago1
TiDB operator hangs after setting the TiDB's `status.report-status` configuration to `false`
Updated 3 months ago1
TiDB operator fails and hangs to update the `status.status-port` in `spec.tidb.config`
Updated 3 months ago
Release 1.6.1
Closed 3 months ago
Backup cleanup taks fail when using azure storage account and Kubernetes
Updated 3 months ago
The backup cleaner can't clean the CR at the schedule phase before task start
Closed 3 months ago
expose tikv metrics port in tikv peer service
Updated 3 months ago
backupManager: truncate the log from the br binary
Closed 4 months ago
tidb spec support loadBalancerClass
Closed 4 months ago1
Does tidb-operator have no requirements for the k8s version? Are any version of k8s and any version of tidb-operator compatible?
Updated 4 months ago1
TiDB-operator fails to start the tiproxy servers if spec.tiproxy.version not provided
Updated 4 months ago5
TiDB operator cannot scale up the tiflash after scaling down to 0
Updated 4 months ago3
TiDB-operator is unable to delete TiProxy servers
Updated 4 months ago2
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 5 months 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 5 months ago1
tikv crash during volumerestore [restore for 5577]
Updated 5 months ago1
volumebackup will failed when there is more than 50 tags specified in snapshot [restore for 5540]
Updated 5 months ago1
volumebackup failed when backup restored cluster [restore for 5537]
Updated 5 months ago1
Stuck restore during data restore caused by stale peer [restore for 5531]
Updated 5 months 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 5 months ago1
volumebackup failed, error message is "init job deleted before all the volume snapshots are created" [restore for 5478]
Updated 5 months 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 5 months ago1
TiKV failed for more than 5 minutes, and the system did not set the backup task as failed [restore for 5439]
Updated 5 months 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 5 months 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 5 months ago1
volumeback failed. reason is "Pod backup-fed-ebs-tidb-operator-ebs-1-init-w5glk has failed, original reason " [restore for 5330]
Updated 5 months ago1
do volumebackup after scaling out cluster, backup failed [restore for 5306]
Updated 5 months ago1
delete restore data pod when restoring will cause restore progress stuck [restore for 5297]
Updated 5 months ago1
kill restore-data pod will cause restore failed [restore for 5295]
Updated 5 months ago1
TiKV failure last for 1 minute can cause backup failure [restore for 5294]
Updated 5 months ago1
When the restore data pod fails, the volumerestore task status is not set to failed [restore for 5293]
Updated 5 months ago1
it is recommended to check the number of tikv volumes when restoring [restore for 5287]
Updated 5 months 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 5 months ago1
The EBS backup task may cause the import task to fail [restore for 5282]
Updated 5 months ago1
backup job is stuck(snapshot is completed) [restore for 5281]
Updated 5 months ago1
there are 2 running volumebackup during volumebackupschedule [restore for 5271]
Updated 5 months ago1