Resync status relaying #615

Open
opened 2023-08-16 12:38:30 +00:00 by jpds · 1 comment
Contributor

I have observed that in a 3 zone deployment (A, B, C), if:

  1. Zone A loses connectivity to C
  2. B retains connectivity to both
  3. Gateway at A sends data to both A, and B (ensuring write-quorum)
  4. B will send the data to C with a resync
  5. A and C both then report resync errors as they have no way to communicate

However all three zones have their requisite blocks, whilst the full mesh should be there normally - it may be useful to have some way for C to inform A (through B) that all blocks are accounted for.

I have observed that in a 3 zone deployment (A, B, C), if: 1. Zone A loses connectivity to C 2. B retains connectivity to both 3. Gateway at A sends data to both A, and B (ensuring write-quorum) 4. B will send the data to C with a resync 5. A and C both then report resync errors as they have no way to communicate However all three zones have their requisite blocks, whilst the full mesh should be there normally - it may be useful to have some way for C to inform A (through B) that all blocks are accounted for.
Owner

Hi, sorry for not answering this earlier. I'm classifying this as low priority, as it doesn't impact Garage's correctness or stability. I'll see what I can do if I have time, but fixing this entirely could end up being a lot of work.

Hi, sorry for not answering this earlier. I'm classifying this as low priority, as it doesn't impact Garage's correctness or stability. I'll see what I can do if I have time, but fixing this entirely could end up being a lot of work.
lx added the
prio
low
label 2023-09-04 12:54:43 +00:00
Sign in to join this conversation.
No milestone
No project
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#615
No description provided.