[tahoe-dev] [tahoe-lafs] #778: "shares of happiness" is the wrong measure; "servers of happiness" is better

tahoe-lafs trac at allmydata.org
Mon Aug 17 00:30:02 UTC 2009


#778: "shares of happiness" is the wrong measure; "servers of happiness" is
better
--------------------------------+-------------------------------------------
 Reporter:  zooko               |           Owner:           
     Type:  defect              |          Status:  new      
 Priority:  critical            |       Milestone:  undecided
Component:  code-peerselection  |         Version:  1.4.1    
 Keywords:  reliability         |   Launchpad_bug:           
--------------------------------+-------------------------------------------

Comment(by kevan):

 hm. How would that work for users like metacrob, who have only one storage
 node? If they set {{{servers_of_happiness=1}}}, they get an error, and if
 they set {{{servers_of_happiness=3}}} (assuming that {{{k}}} stays as a
 default), then they get another error (because there aren't enough servers
 to honor their preference). Maybe I'm misunderstanding something

 To fix this, I propose that if there is no happy config value set, we
 ignore it (by, e.g.,

 {{{
 DEP["happy"] = 0 # or some other constant that the rest of the program can
 interpret
 ...
 DEP["happy"] = int(self.get_config("client", "shares.happy",
 DEP["happy"]))
 }}}
 or something similar), and do not enforce {{{servers_of_happiness}}}. If
 the value is set, and is less than {{{k}}}, we error out as you suggest.

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


More information about the tahoe-dev mailing list