[tahoe-dev] [tahoe-lafs] #200: writing of shares is fragile and/or there is no graceful shutdown

tahoe-lafs trac at allmydata.org
Wed Oct 28 15:11:10 UTC 2009


#200: writing of shares is fragile and/or there is no graceful shutdown
-----------------------------------+----------------------------------------
 Reporter:  zooko                  |           Owner:  warner    
     Type:  enhancement            |          Status:  new       
 Priority:  major                  |       Milestone:  eventually
Component:  code-storage           |         Version:  0.6.1     
 Keywords:  integrity reliability  |   Launchpad_bug:            
-----------------------------------+----------------------------------------

Comment(by zooko):

 This isn't an integrity issue because even if a share is corrupted due to
 this issue that doesn't threaten the integrity of the file.

 Note that there are in general two possible ways to reduce the problem of
 shares being corrupted during a shutdown or crash.  One is to make the
 writing of shares be more robust, for example by writing out a complete
 new copy of the share to a new temporary location and then renaming it
 into place.  This is the option that increases I/O costs as discussed in
 the initial comment.  Another is to add a "graceful shutdown" option where
 the storage server gets a chance to finish (or abort) updating a share
 before its process is killed.

 I'm currently opposed to the latter and would be happier with the current
 fragile update than with the latter.

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/200#comment:3>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid


More information about the tahoe-dev mailing list