[tahoe-lafs-trac-stream] [tahoe-lafs] #1670: KeyError in mutable retrieve

tahoe-lafs trac at tahoe-lafs.org
Mon Jun 18 18:21:43 UTC 2012


#1670: KeyError in mutable retrieve
-------------------------+-------------------------------------------------
     Reporter:  vikarti  |      Owner:  zooko
         Type:  defect   |     Status:  assigned
     Priority:           |  Milestone:  1.9.2
  critical               |    Version:  1.9.1
    Component:  code-    |   Keywords:  mutable retrieve error tahoe-backup
  mutable                |  regression
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by davidsarah):

 Replying to [comment:16 zooko]:
 > please consider the question of whether we should simplify handling of
 !UncoordinatedWriteError as suggested in comment:15.

 Well, it looks like there is quite a lot of code to support the retrying
 of mutable operations, so I assumed that was certainly intentional (it was
 there before I joined the project, and I was mildly surprised since it
 seemed not entirely consistent with the "prime coordination directive").
 Let's redesign it as part of designing two-phase commit, but not before
 1.11. I really want to get 1.10 out with all the changes already on trunk,
 without making any more significant design changes.

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


More information about the tahoe-lafs-trac-stream mailing list