[tahoe-lafs-trac-stream] [tahoe-lafs] #1679: Nondeterministic NoSharesError for direct CHK download in 1.8.3 and 1.9.1

[tahoe-lafs]

#1679: Nondeterministic NoSharesError for direct CHK download in 1.8.3 and 1.9.1
--------------------------+------------------------------------
     Reporter:  nejucomo  |      Owner:  nejucomo
         Type:  defect    |     Status:  new
     Priority:  critical  |  Milestone:  soon
    Component:  code      |    Version:  1.8.3
   Resolution:            |   Keywords:  download heisenbug lae
Launchpad Bug:            |
--------------------------+------------------------------------

Comment (by zooko):

 I don't think the 5xx errors from S3 could have been the sole cause of
 this bug, because this bug happened repeatably, and those S3 5xx errors
 were rare. Zancas measured them -- I forget, but I think it was about 3%
 of requests failed. Anyway, I think that at least in some configurations
 nejucomo's file would fail to be retrieved *every time*, which rules out
 the occasional S3 failures as the cause of that bug.

 However, this does sound a lot like the bug that thedod recently reported
 which was 100% reproducible, which had the strange feature that a "check
 --verify" on a file would succeed but a "get" on that same file would fail
 (in both cases with 100% reproducibility). If thedod gives permission,
 I'll attach his log showing this happening. That bug -- thedod's went away
 when he upgraded the storage-client (gateway) from Tahoe-LAFS v1.8.3 to
 Tahoe-LAFS v1.9.2.

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