[tahoe-lafs-trac-stream] [Tahoe-LAFS] #1449: drop-upload: updates to files may be lost if few servers are connected (e.g. soon after starting the gateway)
Tahoe-LAFS
trac at tahoe-lafs.org
Thu Apr 23 01:24:54 UTC 2015
#1449: drop-upload: updates to files may be lost if few servers are connected
(e.g. soon after starting the gateway)
-------------------------------------+-------------------------------------
Reporter: davidsarah | Owner: daira
Type: defect | Status: assigned
Priority: major | Milestone: 1.11.0
Component: code-frontend-drop- | Version: 1.8.2
upload | Keywords: drop-upload
Resolution: | preservation docs error otf-magic-
Launchpad Bug: | folder-objective2
-------------------------------------+-------------------------------------
Comment (by dawuud):
I think this:
https://github.com/david415/tahoe-lafs/blob/2406.otf-objective-2.3.1-fix-
upload-deque/src/allmydata/client.py#L349-L353
is bad because it may cause unbalanced share allocation to storage
servers. It seems likely that only connecting to K or H+1 servers would
caused a single file's shares to be clustered on a smaller number of
servers... meaning that some individual servers will get more than one
share from that same file. This is bad... especially given that we do not
yet have a "rebalancing" commandline tool of any kind.
--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1449#comment:19>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list