#1293 assigned defect

servers-of-happiness is too conservative when K = 1 — at Version 4

Reported by: davidsarah Owned by: davidsarah
Priority: major Milestone: soon
Component: code Version: 1.8.1
Keywords: servers-of-happiness usability availability unfinished-business Cc:
Launchpad Bug:

Description (last modified by markberger)

When K = 1, any single share is sufficient to reconstruct the file. However, the servers-of-happiness code will still require that there are H servers with unique share numbers. It should not care about the share numbers.

(We knew of examples with small K where the maximum matching definition of servers-of-happiness was conservative relative to the original definition, e.g. 778#comment:198. However, for K > 1 it is more space-efficient to use the maximum matching definition. For K = 1 it is not.)

Change History (4)

comment:1 Changed at 2011-01-06T00:32:21Z by davidsarah

  • Milestone changed from 1.9.0 to 1.8.2
  • Owner changed from somebody to davidsarah
  • Status changed from new to assigned

comment:2 Changed at 2011-01-18T08:25:28Z by zooko

  • Milestone changed from 1.8.2 to 1.9.0

I think we're out of time for 1.8.2. (Apologies if you're actually still intending to do this for 1.8.2.)

comment:3 Changed at 2011-07-24T22:42:30Z by davidsarah

  • Milestone changed from 1.9.0 to 1.10.0

It makes sense to fix this at the same time as Kevan's changes to share placement behaviour in #1382, which will not be in 1.9.

comment:4 Changed at 2013-08-28T15:19:13Z by markberger

  • Description modified (diff)

For example, if we have a share distribution like this:

  • Server A: [1]
  • Server B: [1]
  • Server C: [1]

with k = 1 and h = 3, the placement will be considered unhealthy even though we don't care about the share numbers because any single share is sufficient to reconstruct the file.

Last edited at 2013-08-29T23:10:23Z by zooko (previous) (diff)
Note: See TracTickets for help on using tickets.