Changes between Initial Version and Version 1 of Ticket #1653


Ignore:
Timestamp:
2012-03-12T19:12:36Z (13 years ago)
Author:
davidsarah
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1653

    • Property Keywords preservation mutable retrieve added

  • Ticket #1653 – Description

    initial v1  
    11retrieve.py is currently rather punitive when it detects corrupt shares: it stops using *any* shares from the same server. This doesn't have much effect when there are plenty of servers and the shares are spread thinly, but in small personal grids, a single corrupt share could disqualify enough shares that the retrieve fails.
    22
    3 I think this behavior was copied from the odld immutable downloader. The new immutable downloader doesn't do this: it treats each share independently.
     3I think this behavior was copied from the old immutable downloader. The new immutable downloader doesn't do this: it treats each share independently.
    44
    55To fix this, {{{_mark_bad_share}}} and {{{_remove_reader}}} should remove just the one share from {{{self.remaining_sharemap}}}, instead of all shares with the same server. We also need to look for other calls to {{{_remove_reader()}}}, since I think there may be some which *are* supposed to stop all shares from the same server.