Skip to content
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

tidb-operator volume-snapshot restore failure when tikv request cpu less or equal to 1 #14017

Closed
fengou1 opened this issue Jan 4, 2023 · 1 comment · Fixed by #14153
Closed
Labels
affects-6.5 severity/minor type/bug The issue is confirmed as a bug.

Comments

@fengou1
Copy link
Contributor

fengou1 commented Jan 4, 2023

Bug Report

operator tikv configuration

    requests:
      cpu: 1
      memory: 4Gi
      storage: 20Gi

following https://docs.pingcap.com/zh/tidb-in-kubernetes/stable/restore-from-aws-s3-by-snapshot to do the volume snapshot restore.

What version of TiKV are you using?

v6.5.0

What operating system and CPU are you using?

centos

Steps to reproduce

  1. perform volume-snapshot backup following https://docs.pingcap.com/zh/tidb-in-kubernetes/stable/backup-to-aws-s3-by-snapshot
  2. perform volume-snapshot restore following https://docs.pingcap.com/zh/tidb-in-kubernetes/stable/restore-from-aws-s3-by-snapshot to do the volume snapshot restore.

What did you expect?

restore shall be success

What did happened?

restore failure with the following error
[2023/01/04 10:00:19.751 +00:00] [FATAL] [[setup.rs:309](http://setup.rs:309/)] ["invalid configuration: max_background_jobs should be greater than 0 and less than or equal to 20"]

@fengou1
Copy link
Contributor Author

fengou1 commented Feb 7, 2023

/remove affects-5.4

ti-chi-bot added a commit that referenced this issue Feb 7, 2023
…s configuration (#14153)

close #14017

Signed-off-by: fengou1 <feng.ou@pingcap.com>

Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
ti-chi-bot pushed a commit to ti-chi-bot/tikv that referenced this issue Feb 7, 2023
close tikv#14017

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
ti-chi-bot pushed a commit to ti-chi-bot/tikv that referenced this issue Feb 7, 2023
close tikv#14017

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
ti-chi-bot pushed a commit to ti-chi-bot/tikv that referenced this issue Feb 7, 2023
close tikv#14017

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
ti-chi-bot pushed a commit that referenced this issue Feb 15, 2023
…s configuration (#14229)

close #14017

Signed-off-by: fengou1 <feng.ou@pingcap.com>
ti-chi-bot added a commit that referenced this issue Feb 15, 2023
close #13586, close #13752, ref #14017, ref #14084

Signed-off-by: Andrei Dragus <andrei.dragus@databricks.com>

Co-authored-by: Andrei Dragus <andrei.dragus@databricks.com>
Co-authored-by: Xinye Tao <xy.tao@outlook.com>
ti-chi-bot added a commit that referenced this issue Mar 27, 2023
close #13586, close #13752, ref #14017, ref #14084

Signed-off-by: Andrei Dragus <andrei.dragus@databricks.com>

Co-authored-by: Andrei Dragus <andrei.dragus@databricks.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-6.5 severity/minor type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants