Changes between Initial Version and Version 1 of Ticket #661


Ignore:
Timestamp:
2009-03-11T22:07:16Z (16 years ago)
Author:
zooko
Comment:

I reformatted the original description so that trac will represent the numbered items as a list.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #661 – Description

    initial v1  
    11Dynamic share repair to maintain file health.
    22based on the following features already exist in Allmydata-Tahoe1.3 we can improve automatic repair:
     3
    341. Foolscap provides the knowledge of the alive nodes.
     5
    462. Verification of file availability can be delegated to other node through read-cap or a verify-cap without security risk.
     7
    58The proposed auto repair process:
     9
    6101. Using memory-based algorithm, because client know where the file shares exist so we can keep tack of alive file shares, for simplicity we consider that share availability from its node availability.
     11
    7122. repair process triggered automatically from the repairer, repair responsibility has many technique based repair cost ; network bandwidth and fault tolerant.
    8 3.time out , we can use lazy repair technique to avoid node temporary node failure, i.e waiting for a certain time before repair process starts.
    9 4.reintegration, using memory-based repair technique remembering failed storage servers, who come back to life, will help in reducing Tahoe grid resources such as network bandwidth and storage space.
     13
     143. time out , we can use lazy repair technique to avoid node temporary node failure, i.e waiting for a certain time before repair process starts.
     15
     164. reintegration, using memory-based repair technique remembering failed storage servers, who come back to life, will help in reducing Tahoe grid resources such as network bandwidth and storage space.
     17
    10185. repairer, selection of repair responsibly takes many issues into consideration: security , repairer location , repairer resources.