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.

Sign up for GitHub

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

Jump to bottom

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

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

fengou1 opened this issue Jan 4, 2023 · 1 comment · Fixed by #14153
Labels
affects-6.5 This bug affects the 6.5.x(LTS) versions. 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"]
@andreid-db andreid-db mentioned this issue Jan 26, 2023
Merged
@tabokie tabokie added type/bug The issue is confirmed as a bug. severity/minor affects-5.4 This bug affects the 5.4.x(LTS) versions. affects-6.0 affects-6.1 This bug affects the 6.1.x(LTS) versions. affects-6.2 affects-6.3 affects-6.4 affects-6.5 This bug affects the 6.5.x(LTS) versions. labels Jan 29, 2023
ti-chi-bot pushed a commit that referenced this issue Jan 29, 2023
@andreid-db
config: allow starting TiKV nodes with <1 CPU (#14084)
c353910 
close #13586, close #13752, ref #14017

Signed-off-by: Andrei Dragus <andrei.dragus@databricks.com>
This was referenced Jan 29, 2023
Open
Merged
Merged
@fengou1 fengou1 mentioned this issue Feb 7, 2023
Merged
@fengou1
Copy link
Contributor Author

fengou1 commented Feb 7, 2023

/remove affects-5.4

@jebter jebter removed affects-5.4 This bug affects the 5.4.x(LTS) versions. affects-6.0 affects-6.1 This bug affects the 6.1.x(LTS) versions. affects-6.2 affects-6.3 affects-6.4 labels Feb 7, 2023
ti-chi-bot added a commit that referenced this issue Feb 7, 2023
@fengou1 @ti-chi-bot
fix: ebs volume snapshot support tikv node equipped with 2 cpu or les…
adff03c 
…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 ti-chi-bot mentioned this issue Feb 7, 2023
Closed
ti-chi-bot pushed a commit to ti-chi-bot/tikv that referenced this issue Feb 7, 2023
@fengou1 @ti-chi-bot
This is an automated cherry-pick of tikv#14153
4c5caf6 
close tikv#14017

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
@ti-chi-bot ti-chi-bot mentioned this issue Feb 7, 2023
Closed
ti-chi-bot pushed a commit to ti-chi-bot/tikv that referenced this issue Feb 7, 2023
@fengou1 @ti-chi-bot
This is an automated cherry-pick of tikv#14153
89a15ce 
close tikv#14017

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
@ti-chi-bot ti-chi-bot mentioned this issue Feb 7, 2023
Closed
ti-chi-bot pushed a commit to ti-chi-bot/tikv that referenced this issue Feb 7, 2023
@fengou1 @ti-chi-bot
This is an automated cherry-pick of tikv#14153
0efcc94 
close tikv#14017

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
@fengou1 fengou1 mentioned this issue Feb 15, 2023
Merged
ti-chi-bot pushed a commit that referenced this issue Feb 15, 2023
@fengou1
fix: ebs volume snapshot support tikv node equipped with 2 cpu or les…
c987f8a 
…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
@ti-chi-bot @andreid-db @tabokie
config: allow starting TiKV nodes with <1 CPU (#14084) (#14091)
5cdc134 
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
@ti-chi-bot @andreid-db
config: allow starting TiKV nodes with <1 CPU (#14084) (#14090)
339ec83 
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
Assignees
No one assigned
Labels
affects-6.5 This bug affects the 6.5.x(LTS) versions. severity/minor type/bug The issue is confirmed as a bug.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: ebs volume snapshot support tikv node equipped with 2 cpu or less configuration fengou1/tikv
3 participants
@jebter @tabokie @fengou1