[tahoe-lafs-trac-stream] [tahoe-lafs] #2110: uploader confuses self-write-dedup with "server is full"

[tahoe-lafs]

#2110: uploader confuses self-write-dedup with "server is full"
-------------------------+--------------------------
     Reporter:  zooko    |      Owner:  markberger
         Type:  defect   |     Status:  new
     Priority:  normal   |  Milestone:  undecided
    Component:  unknown  |    Version:  1.10.0
   Resolution:           |   Keywords:  upload error
Launchpad Bug:           |
-------------------------+--------------------------

Comment (by zooko):

 Replying to [comment:1 daira]:
 > We should certainly do better error reporting, but ideally both uploads
 should succeed. That seems a bit complicated to implement with the current
 protocol though.

 That does sound desirable but complicated to me. I guess it would require
 the second uploader — the one who is not actually transferring the
 ciphertext — to check back later and see if the first uploader finished
 transferring the correct ciphertext or not. There might also need to be
 some kind of timeout/conflict/retry/2PC protocol in case the second
 uploader decide that the first alleged uploader is unacceptably
 slow/stalled/DoS'ing. How about if we add this issue to #1851?

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2110#comment:2>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage