Changes between Initial Version and Version 1 of Ticket #546


Ignore:
Timestamp:
2008-12-09T18:45:53Z (15 years ago)
Author:
warner
Comment:

update bug numbers, clarify the specific focus of this bug (surprise shares cause UCWE)

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #546 – Description

    initial v1  
    1010
    1111 * problem 1: mapupdate(MODE_WRITE) triggers on 1000, when it should use 1000$
    12    (to avoid triggering on 10001)
     12   (to avoid triggering on 10001) (ticket #547)
    1313
    1414 * problem 2: the mapupdate can hit a false boundary because the inserted gap
    1515   was too large. It might be a good idea to increase epsilon for MODE_WRITE
    16    to reduce the chance of this.
     16   to reduce the chance of this. (ticket #549)
    1717
    1818 * problem 3: when mapupdate hits a false boundary (because of either of the
    … …  
    2020   actually already have them. The code looks for these "surprise" shares and
    2121   raises UCWE if it sees them. The UCWE is probably inappropriate, instead a
    22    new writev should be sent to update the old share.
     22   new writev should be sent to update the old share. (this ticket, #546)
    2323
    2424 * problem 4: delete() which hits UCWE (because of problem 3, or other issues)
    2525   will retry, but will fail the second time because must_exist=True is the
    26    default
     26   default (ticket #550)
    2727
    2828
    … …  
    9191servers) is incorrectly triggered (the pattern-match looks for "1000" but it
    9292should really look for "1000$", to avoid matching on "10001"). But that is in
    93 a different ticket.
     93a different ticket (#547).
    9494
    95 This ticket is about the fact that inserting a large batch of new servers can
    96 confuse the boundary-matching code.
     95This ticket is about the fact that the publish process doesn't keep track of
     96which shares it's sent to whom, so if it needs to make a second pass (to
     97place shares that were not accepted by their first destination), it will get
     98confused and signal an inappropriate UCWE.
    9799
    98100When a single new server is added, it is effectively inserted at a random