mapupdate(MODE_WRITE) triggers on a false boundary #547
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#547
Loading…
Reference in New Issue
Block a user
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?
"problem 1" in #546, is that the mapupdate code has a bug, in which it
triggers too early. The MODE_WRITE logic waits for the following conditions:
versions that have that sequence number
The last criteria is intended to help us find the edge of the "active set":
the boundary between servers who have shares (at the beginning of the
permuted list) and those who do not (at the end of the list). The bug is in
the way this last criteria is tested.
If we've queried 10 servers and received responses from 9 of them, in the
pattern "00100010?1", the logic that looks for "1000" will fire:
Instead, the logic should be more like "1000$". At least it should not be
allowed to fire if there are any share-holding servers beyond the match.
The consequence of this bug is to exacerbate the problems in #546: sending
shares to servers which already have other shares, triggering inappropriate
UncoordinatedWriteErrors.
Attachment cryptic_notes.txt (1630 bytes) added
It's really bothering me that mutable file upload and download behavior is so finicky, buggy, inefficient, hard to understand, different from immutable file upload and download behavior, etc. So I'm putting a bunch of tickets into the "1.8" Milestone. I am not, however, at this time, volunteering to work on these tickets, so it might be a mistake to put them into the 1.8 Milestone, but I really hope that someone else will volunteer or that I will decide to do it myself. :-)
If you like this ticket, you might like #540 (inappropriate "uncoordinated write error" after handling a server failure).