-
Notifications
You must be signed in to change notification settings - Fork 499
Issues: pingcap/tidb-operator
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
TiDB operator cannot scale up the tiflash after scaling down to 0
#5834
opened Nov 4, 2024 by
kos-team
TiDB-operator fails to start the tiproxy servers if spec.tiproxy.version not provided
#5833
opened Nov 4, 2024 by
kos-team
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]
area/ebs-br
type/bug
Something isn't working
#5821
opened Oct 25, 2024 by
ti-chi-bot
tikv crash during volumerestore [restore for 5577]
area/ebs-br
type/bug
Something isn't working
#5819
opened Oct 25, 2024 by
ti-chi-bot
volumebackup will failed when there is more than 50 tags specified in snapshot [restore for 5540]
area/ebs-br
type/bug
Something isn't working
#5818
opened Oct 25, 2024 by
ti-chi-bot
volumebackup failed when backup restored cluster [restore for 5537]
area/ebs-br
type/bug
Something isn't working
#5817
opened Oct 25, 2024 by
ti-chi-bot
Stuck restore during data restore caused by stale peer [restore for 5531]
area/ebs-br
type/bug
Something isn't working
#5816
opened Oct 25, 2024 by
ti-chi-bot
If there is a PV with the same name (released status) in the namespace, it will cause the restore to fail [restore for 5505]
area/ebs-br
type/bug
Something isn't working
#5815
opened Oct 25, 2024 by
ti-chi-bot
volumebackup failed, error message is "init job deleted before all the volume snapshots are created" [restore for 5478]
area/ebs-br
type/bug
Something isn't working
#5814
opened Oct 25, 2024 by
ti-chi-bot
TiKV failed for more than 5 minutes, and the system did not set the backup task as failed [restore for 5439]
area/ebs-br
type/bug
Something isn't working
#5812
opened Oct 25, 2024 by
ti-chi-bot
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]
area/ebs-br
type/bug
Something isn't working
#5811
opened Oct 25, 2024 by
ti-chi-bot
When checking whether warmup has ended, if there are warmup jobs in other namespaces, it will interfere with the current results. [restore for 5405]
area/ebs-br
type/bug
Something isn't working
#5810
opened Oct 25, 2024 by
ti-chi-bot
volumeback failed. reason is "Pod backup-fed-ebs-tidb-operator-ebs-1-init-w5glk has failed, original reason " [restore for 5330]
area/ebs-br
type/bug
Something isn't working
#5809
opened Oct 25, 2024 by
ti-chi-bot
do volumebackup after scaling out cluster, backup failed [restore for 5306]
area/ebs-br
type/bug
Something isn't working
#5808
opened Oct 25, 2024 by
ti-chi-bot
delete restore data pod when restoring will cause restore progress stuck [restore for 5297]
area/ebs-br
type/bug
Something isn't working
#5807
opened Oct 25, 2024 by
ti-chi-bot
kill restore-data pod will cause restore failed [restore for 5295]
area/ebs-br
type/bug
Something isn't working
#5806
opened Oct 25, 2024 by
ti-chi-bot
TiKV failure last for 1 minute can cause backup failure [restore for 5294]
area/ebs-br
type/bug
Something isn't working
#5805
opened Oct 25, 2024 by
ti-chi-bot
When the restore data pod fails, the volumerestore task status is not set to failed [restore for 5293]
area/ebs-br
type/bug
Something isn't working
#5804
opened Oct 25, 2024 by
ti-chi-bot
Previous Next
ProTip!
no:milestone will show everything without a milestone.