Changes between Version 1 and Version 2 of Ticket #661


Ignore:
Timestamp:
2009-03-12T21:03:22Z (16 years ago)
Author:
warner
Comment:

re-reformatted it: I think trac requires the leading space to trigger the "display as list" formatter

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #661 – Description

    v1 v2  
    1 Dynamic share repair to maintain file health.
    2 based on the following features already exist in Allmydata-Tahoe1.3 we can improve automatic repair:
     1Dynamic share repair to maintain file health. based on the following features
     2already exist in Allmydata-Tahoe1.3 we can improve automatic repair:
    33
    4 1. Foolscap provides the knowledge of the alive nodes.
     4 1. Foolscap provides the knowledge of the alive nodes.
    55
    6 2. Verification of file availability can be delegated to other node through read-cap or a verify-cap without security risk.
     6 2. Verification of file availability can be delegated to other node through
     7    read-cap or a verify-cap without security risk.
    78
    89The proposed auto repair process:
    910
    10 1. 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 1. Using memory-based algorithm, because client know where the file shares
     12    exist so we can keep tack of alive file shares, for simplicity we
     13    consider that share availability from its node availability.
    1114
    12 2. repair process triggered automatically from the repairer, repair responsibility has many technique based repair cost ; network bandwidth and fault tolerant.
     15 2. repair process triggered automatically from the repairer, repair
     16    responsibility has many technique based repair cost ; network bandwidth
     17    and fault tolerant.
    1318
    14 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.
     19 3. time out , we can use lazy repair technique to avoid node temporary node
     20    failure, i.e waiting for a certain time before repair process starts.
    1521
    16 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.
     22 4. reintegration, using memory-based repair technique remembering failed
     23    storage servers, who come back to life, will help in reducing Tahoe grid
     24    resources such as network bandwidth and storage space.
    1725
    18 5. repairer, selection of repair responsibly takes many issues into consideration: security , repairer location , repairer resources.
     26 5. repairer, selection of repair responsibly takes many issues into
     27    consideration: security , repairer location , repairer resources.