Deuxfleurs/garage
41
56
Fork 73
Code Issues 99 Pull requests 14 Releases 30 Wiki Activity

Garage cluster encounters resync problems and does not seem to recover #911

New issue
Open
opened 2024-12-18 21:09:18 +00:00 by Szetty · 2 comments
Szetty commented 2024-12-18 21:09:18 +00:00
Copy link

We have a Garage cluster deployed in Kubernetes, consisting of 8 nodes with replication factor of 2. We had 6 nodes before, and as we added two more, we needed to do some shifting too so one node is in a different zone now.

Since we switched to 8 nodes there are lot of items in the resync queue and they do not seem to self heal. There are also many resync errors. Not sure how to proceed or what other information might be necessary.

Anyone has any idea what could be the problem ?

We have a Garage cluster deployed in Kubernetes, consisting of 8 nodes with replication factor of 2. We had 6 nodes before, and as we added two more, we needed to do some shifting too so one node is in a different zone now. Since we switched to 8 nodes there are lot of items in the resync queue and they do not seem to self heal. There are also many resync errors. Not sure how to proceed or what other information might be necessary. Anyone has any idea what could be the problem ?
maximilien commented 2024-12-18 21:46:36 +00:00
Owner
Copy link

What is the version of garage you are using? Can you share what your garage status and layout look like? Can you also share the state of the works on a couple of nodes? Did you update the tranquility setting?

Items can be multiple time in the resync queue, so the absolute number of item in the resync queue is not necessarily indicative that nothing is happening.

What is the version of garage you are using? Can you share what your garage status and layout look like? Can you also share the state of the works on a couple of nodes? Did you update the tranquility setting? Items can be multiple time in the resync queue, so the absolute number of item in the resync queue is not necessarily indicative that nothing is happening.
Szetty commented 2024-12-19 07:16:13 +00:00
Author
Copy link

garage stats:

Garage version: v1.0.0 [features: k2v, lmdb, sqlite, consul-discovery, kubernetes-discovery, metrics, telemetry-otlp, bundled-libs]
Rust compiler version: 1.73.0

Database engine: LMDB (using Heed crate)

Table stats:
  Table      Items     MklItems  MklTodo  GcTodo
  bucket_v2  4         5         0        0
  key        4         5         0        0
  object     19710544  25328775  0        0
  version    6235495   7979732   0        0
  block_ref  11549864  15041405  0        0

Block manager stats:
  number of RC entries (~= number of blocks): 11486142
  resync queue length: 2197
  blocks with resync errors: 1321

Storage nodes:
  ID                Hostname  Zone  Capacity  Part.  DataAvail               MetaAvail
  6491f54b516fe740  garage-3  hel1  6.0 TB    64     168.4 GB/7.6 TB (2.2%)  168.4 GB/7.6 TB (2.2%)
  b38df7f1cd6e64cc  garage-5  fsn1  6.0 TB    64     177.5 GB/7.6 TB (2.3%)  177.5 GB/7.6 TB (2.3%)
  c5a65adbdbfcabd8  garage-0  fsn1  6.0 TB    64     108.4 GB/7.6 TB (1.4%)  108.4 GB/7.6 TB (1.4%)
  da04daee442cc468  garage-1  hel1  6.0 TB    64     304.9 GB/7.6 TB (4.0%)  304.9 GB/7.6 TB (4.0%)
  fecb40744431de50  garage-2  fsn1  6.0 TB    64     172.3 GB/7.6 TB (2.3%)  172.3 GB/7.6 TB (2.3%)
  dd93d29d89331ec7  garage-7  hel1  6.0 TB    64     7.2 TB/7.6 TB (93.9%)   7.2 TB/7.6 TB (93.9%)
  a657965c7aaf3281  garage-4  fsn1  6.0 TB    64     119.6 GB/7.6 TB (1.6%)  119.6 GB/7.6 TB (1.6%)
  8b4e87778d470a0b  garage-6  hel1  6.0 TB    64     7.2 TB/7.6 TB (94.6%)   7.2 TB/7.6 TB (94.6%)

Estimated available storage space cluster-wide (might be lower in practice):
  data: 433.5 GB
  metadata: 433.5 GB

garage status:

==== HEALTHY NODES ====
ID                Hostname  Address              Tags        Zone  Capacity  DataAvail
fecb40744431de50  garage-2  10.233.122.237:3901  [garage-2]  fsn1  6.0 TB    172.6 GB (2.3%)
dd93d29d89331ec7  garage-7  10.233.66.60:3901    [garage-7]  hel1  6.0 TB    7.2 TB (93.9%)
c5a65adbdbfcabd8  garage-0  10.233.67.134:3901   [garage-0]  fsn1  6.0 TB    108.4 GB (1.4%)
6491f54b516fe740  garage-3  10.233.100.211:3901  [garage-3]  hel1  6.0 TB    168.6 GB (2.2%)
b38df7f1cd6e64cc  garage-5  10.233.64.58:3901    [garage-5]  fsn1  6.0 TB    177.8 GB (2.3%)
da04daee442cc468  garage-1  10.233.103.22:3901   [garage-1]  hel1  6.0 TB    303.9 GB (4.0%)
8b4e87778d470a0b  garage-6  10.233.72.241:3901   [garage-6]  hel1  6.0 TB    7.2 TB (94.6%)
a657965c7aaf3281  garage-4  10.233.115.160:3901  [garage-4]  fsn1  6.0 TB    119.6 GB (1.6%)

garage layout show:

==== CURRENT CLUSTER LAYOUT ====
ID                Tags      Zone  Capacity  Usable capacity
6491f54b516fe740  garage-3  hel1  6.0 TB    6.0 TB (100.0%)
8b4e87778d470a0b  garage-6  hel1  6.0 TB    6.0 TB (100.0%)
a657965c7aaf3281  garage-4  fsn1  6.0 TB    6.0 TB (100.0%)
b38df7f1cd6e64cc  garage-5  fsn1  6.0 TB    6.0 TB (100.0%)
c5a65adbdbfcabd8  garage-0  fsn1  6.0 TB    6.0 TB (100.0%)
da04daee442cc468  garage-1  hel1  6.0 TB    6.0 TB (100.0%)
dd93d29d89331ec7  garage-7  hel1  6.0 TB    6.0 TB (100.0%)
fecb40744431de50  garage-2  fsn1  6.0 TB    6.0 TB (100.0%)

Zone redundancy: maximum

Current cluster layout version: 4

Can you also share the state of the works on a couple of nodes?

Not sure what to share exactly, we have logs and metrics in Grafana if that can help

Did you update the tranquility setting?

As I see this would be a type of repair (related to scrubs), the only repair I tried was garage repair --all-nodes --yes tables, run multiple times.

`garage stats`: ``` Garage version: v1.0.0 [features: k2v, lmdb, sqlite, consul-discovery, kubernetes-discovery, metrics, telemetry-otlp, bundled-libs] Rust compiler version: 1.73.0 Database engine: LMDB (using Heed crate) Table stats: Table Items MklItems MklTodo GcTodo bucket_v2 4 5 0 0 key 4 5 0 0 object 19710544 25328775 0 0 version 6235495 7979732 0 0 block_ref 11549864 15041405 0 0 Block manager stats: number of RC entries (~= number of blocks): 11486142 resync queue length: 2197 blocks with resync errors: 1321 Storage nodes: ID Hostname Zone Capacity Part. DataAvail MetaAvail 6491f54b516fe740 garage-3 hel1 6.0 TB 64 168.4 GB/7.6 TB (2.2%) 168.4 GB/7.6 TB (2.2%) b38df7f1cd6e64cc garage-5 fsn1 6.0 TB 64 177.5 GB/7.6 TB (2.3%) 177.5 GB/7.6 TB (2.3%) c5a65adbdbfcabd8 garage-0 fsn1 6.0 TB 64 108.4 GB/7.6 TB (1.4%) 108.4 GB/7.6 TB (1.4%) da04daee442cc468 garage-1 hel1 6.0 TB 64 304.9 GB/7.6 TB (4.0%) 304.9 GB/7.6 TB (4.0%) fecb40744431de50 garage-2 fsn1 6.0 TB 64 172.3 GB/7.6 TB (2.3%) 172.3 GB/7.6 TB (2.3%) dd93d29d89331ec7 garage-7 hel1 6.0 TB 64 7.2 TB/7.6 TB (93.9%) 7.2 TB/7.6 TB (93.9%) a657965c7aaf3281 garage-4 fsn1 6.0 TB 64 119.6 GB/7.6 TB (1.6%) 119.6 GB/7.6 TB (1.6%) 8b4e87778d470a0b garage-6 hel1 6.0 TB 64 7.2 TB/7.6 TB (94.6%) 7.2 TB/7.6 TB (94.6%) Estimated available storage space cluster-wide (might be lower in practice): data: 433.5 GB metadata: 433.5 GB ``` `garage status`: ``` ==== HEALTHY NODES ==== ID Hostname Address Tags Zone Capacity DataAvail fecb40744431de50 garage-2 10.233.122.237:3901 [garage-2] fsn1 6.0 TB 172.6 GB (2.3%) dd93d29d89331ec7 garage-7 10.233.66.60:3901 [garage-7] hel1 6.0 TB 7.2 TB (93.9%) c5a65adbdbfcabd8 garage-0 10.233.67.134:3901 [garage-0] fsn1 6.0 TB 108.4 GB (1.4%) 6491f54b516fe740 garage-3 10.233.100.211:3901 [garage-3] hel1 6.0 TB 168.6 GB (2.2%) b38df7f1cd6e64cc garage-5 10.233.64.58:3901 [garage-5] fsn1 6.0 TB 177.8 GB (2.3%) da04daee442cc468 garage-1 10.233.103.22:3901 [garage-1] hel1 6.0 TB 303.9 GB (4.0%) 8b4e87778d470a0b garage-6 10.233.72.241:3901 [garage-6] hel1 6.0 TB 7.2 TB (94.6%) a657965c7aaf3281 garage-4 10.233.115.160:3901 [garage-4] fsn1 6.0 TB 119.6 GB (1.6%) ``` `garage layout show`: ``` ==== CURRENT CLUSTER LAYOUT ==== ID Tags Zone Capacity Usable capacity 6491f54b516fe740 garage-3 hel1 6.0 TB 6.0 TB (100.0%) 8b4e87778d470a0b garage-6 hel1 6.0 TB 6.0 TB (100.0%) a657965c7aaf3281 garage-4 fsn1 6.0 TB 6.0 TB (100.0%) b38df7f1cd6e64cc garage-5 fsn1 6.0 TB 6.0 TB (100.0%) c5a65adbdbfcabd8 garage-0 fsn1 6.0 TB 6.0 TB (100.0%) da04daee442cc468 garage-1 hel1 6.0 TB 6.0 TB (100.0%) dd93d29d89331ec7 garage-7 hel1 6.0 TB 6.0 TB (100.0%) fecb40744431de50 garage-2 fsn1 6.0 TB 6.0 TB (100.0%) Zone redundancy: maximum Current cluster layout version: 4 ``` > Can you also share the state of the works on a couple of nodes? Not sure what to share exactly, we have logs and metrics in Grafana if that can help > Did you update the tranquility setting? As I see this would be a type of repair (related to scrubs), the only repair I tried was `garage repair --all-nodes --yes tables`, run multiple times.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
update-dependencies-1.1
feat-metrics-metadata-engine
improve-secret-error-message
hotfix/1.0.0-rc1-red-ftr-wquorum
main-0.9.x
db-no-unsafe
main-0.8.x
k2v/shared_http_client
feat/website-redir
smithy2
test/compilation
poc/nomad-ci
test-ci-wait
pnet_datalink-0.33.0
optimal-layout
k2v-watch-range
db-debug-log
build-convert-db
demonstrate-cargo2nix-bug
dangerous/no-fsync
dev0.7.3
doc/benchmarks
bug/check_static
bucket-cors-more
storage-optimizations
old-main
v1.0.1
v1.0.0
v0.9.4
v1.0.0-rc1
v0.8.7
v0.9.3
v0.9.2
v0.8.6
v0.9.2-rc1
v0.9.1
v0.8.5
v0.10.0-beta1
v0.9.0
v0.9.0-rc2
v0.9.0-rc1
v0.9.0-beta4
v0.9.0-beta3
v0.9.0-beta2
v0.8.4
v0.9.0-beta1
v0.8.3
v0.8.3-rc1
format_table-v0.1.1
format_table-v0.1.0
v0.8.2
v0.8.1
v0.8.0
v0.8.0-rc2
v0.8.0-rc1
v0.8.0-dangerous-no-fsync
v0.8.0-beta2-k2v
v0.8.0-beta2
v0.8.0-beta1-k2v
v0.8.0-beta1
v0.7.99.3-k2v
v0.7.3
v0.7.3-beta2
v0.7.3-beta1
v0.7.2.1
v0.7.2
v0.7.2_ci-test-2
v0.7.2+ci-test-version
v0.7.99.2-k2v
v0.7.99.1-k2v
v0.7.99-k2v
v0.7.2-k2v
v0.7.1-admin-k2v-2
v0.7.1-admin-k2v
v0.7.1-k2v
v0.7.1
v0.7.0
v0.7.0-rc1
v0.6.1
v0.6.0
v0.6.0-rc1
v0.5.1
v0.5.0.1
v0.5.0
v0.5-beta1
v0.4.0
v0.4-rc2
v0.4-rc1
0.4-beta
0.4-alpha
v0.3.0.2
v0.3.0.1
v0.3.0
v0.2.1.5
v0.2.1
v0.2.0
0.1.1b
0.1.1
0.1.0b
0.1.0
Labels
Clear labels   
action
check-aws
The behaviour should be checked against AWS S3

  
action
discussion-needed
We need to discuss if the feature is desirable and/or better specify the envisioned behavior or technical implementation

  
action
for-external-contributors
Core team does not plan working on this in the near future however an external contribution will be reviewed & merged

  
action
for-newcomers
An issue that should be newcomer friendly.

  
action
more-info-needed
More information is needed to investigate this issue

  
action
need-funding
This issue represents lots of work, we need to find money to pay our core team work

  
action
triage-required
It's not very clear what we want to do with this issue yet, more thoughts is required

  
kind
correctness
Issues of theoretical correctness that may impact edge-case scenarios

  
kind
ideas
For abstract ideas/proposal to make Garage better, to better communicate our not yet achieved aims

  
kind
improvement
Feature requests that do not fall in other categories

  
kind
performance
Deceptive performance observed OR idea to improve performances

  
kind
testing
Functional tests, integration tests, Jepsen, etc.

  
kind
usability
Propositions to make Garage easier to operate, by improving error reporting, CLI, etc.

  
kind
wrong-behavior
Unintended behavior

  
prio
critical
Could impact integrity or availability of production clusters

  
prio
low
For issues that we don't want to spend time on until made absolutely necessary

  
scope
admin-api
Issues concerning the administration API

  
scope
background-healing
Background healing covers repair tasks, anti-entropy, merkle trees, etc. ; everything related to replicating data appropriately.

  
scope
build
Issues with Nix, Drone, Rust Compiler, etc.

  
scope
documentation

  
scope
k8s
Kubernetes related, including Helm Charts

  
scope
layout
Linked to the cluster layout and storage management

  
scope
metadata
Metadata Engine (LMDB, sqlite, etc.)

  
scope
ops
Operations related to operations/maintenance issue, tooling related (like CLI missing info ; impossible, too dangerous, too complicated migration, etc.)

  
scope
rpc
Linked to RPC

  
scope
s3-api
Related to the S3 API (especially compatibility issues).

  
scope
security
Cryptography-related, auth-related, authorization-related issues

  
scope
telemetry
OpenTelemetry (traces, metrics, etc.)

No labels
action
check-aws
action
discussion-needed
action
for-external-contributors
action
for-newcomers
action
more-info-needed
action
need-funding
action
triage-required
kind
correctness
kind
ideas
kind
improvement
kind
performance
kind
testing
kind
usability
kind
wrong-behavior
prio
critical
prio
low
scope
admin-api
scope
background-healing
scope
build
scope
documentation
scope
k8s
scope
layout
scope
metadata
scope
ops
scope
rpc
scope
s3-api
scope
security
scope
telemetry
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Deuxfleurs/garage#911
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?