[tahoe-dev] [tahoe-lafs] #1092: shares.happy is the wrong name of the measure

tahoe-lafs trac at tahoe-lafs.org
Thu Dec 23 06:45:26 UTC 2010


#1092: shares.happy is the wrong name of the measure
--------------------------------+-------------------------------------------
     Reporter:  zooko           |       Owner:  warner          
         Type:  defect          |      Status:  new             
     Priority:  minor           |   Milestone:  eventually      
    Component:  code-nodeadmin  |     Version:  1.7.0           
   Resolution:                  |    Keywords:  usability upload
Launchpad Bug:                  |  
--------------------------------+-------------------------------------------

Comment (by kevan):

 I'm attaching a patch that changes {{{shares.happy}}} to
 {{{servers.happy}}}. The client now ignores {{{shares.happy}}}, since it
 doesn't make a lot of sense to use {{{shares.happy}}} for
 {{{servers.happy}}}, given the differences between the two robustness
 metrics. Should we make the startup code print a warning if it doesn't
 find a {{{servers.happy}}} but does find a {{{shares.happy}}}?

 I've defined {{{servers.happy}}} with the default value of 1; this means
 that servers of happiness checks will be disabled for nodes without a
 {{{servers.happy}}} directive in their {{{tahoe.cfg}}} (including the
 result of {{{tahoe create-node}}}).

 I don't think there's a particularly convincing argument for leaving the
 default at 7; probably the only good it is doing is forcing people to
 reason about their grid when they have to go in and edit {{{tahoe.cfg}}}
 when their uploads fail because their "Hello, world!" grid isn't big
 enough to satisfy {{{servers.happy=7}}}. There are probably friendlier
 ways to do that :-). I'm open to being convinced for a value that isn't 1,
 but I think that there's something to be said for giving the user the
 information that they need to set the value sensibly and staying out of
 their way until they do that.

 (I don't have a clear opinion yet on {{{shares.needed}}}, since I hadn't
 thought about that until I read the ticket this morning)

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1092#comment:1>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage


More information about the tahoe-dev mailing list