premature abort of upload if some shares were already present and some servers fail #608
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#608
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?
There is logic in source:src/allmydata/immutable/encode.py@20090107034822-92b7f-4b8bbe1a2c1bf374154bc1cd32ff8040e998ca00#L474 to abort an upload if there aren't enough remaining shareholders. This fails to take into account that some shares might already have been present on servers before this upload began. So for example if M=10, and there were 5 shares present on servers when you started, and shares_of_happiness is 7, then you'll be talking to 5 landlords, and if one of them disconnects you should not then give up on the whole upload, per this line:
To test this, the test needs to create a file with 10 shares, delete 5 of them, start an upload, and then arrange it that during the upload 3 of the servers fail -- the upload should proceed normally (since share_of_happiness is 7). Also test what happens when 4 of them fail -- the upload should stop immediately.
Eh, this doesn't have to be fixed for tahoe-1.3.0.
I'm going to add cc: tahoe-dev to this ticket, and then I'm going to post the original contents of this ticket to tahoe-dev along with a link to this ticket.
Kevan's patch from #778 ("shares of happiness" is the wrong measure; "servers of happiness" is better) might fix this.
Related to #610 and #873.
#778 did indeed fix this ticket.