Changes between Version 13 and Version 14 of Ticket #1657


Ignore:
Timestamp:
2014-01-21T11:19:56Z (10 years ago)
Author:
amontero
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1657 – Description

    v13 v14  
    2323Here are some issues and how I'm addressing them:
    2424
    25 1. Storage use: I don't want any node to store a full set of shares since it doesn't add security to the grid and it is a waste. I want each member to hold x+1 shares, where x is enough for the file to be readable from that single node. Now I'm acomplishing this by fully repairing the grid on that node isolated and later pruning storage shares down to the desired count with a script (it's dirty, but works). Thinking about it, I've come to the conclusion that a 'hold-no-more-than-Z-shares' kind of setting for storage nodes will help me a lot. Ticket #711 would also be useful. Also #1340 and [https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1212#comment:35 comment on #1212]
     251. Storage use: I don't want any node to store a full set of shares since it doesn't add security to the grid and it is a waste. I want each member to hold x+1 shares, where x is enough for the file to be readable from that single node. Now I'm acomplishing this by fully repairing the grid on that node isolated and later pruning storage shares down to the desired count with a script (it's dirty, but works). Thinking about it, I've come to the conclusion that a 'hold-no-more-than-Z-shares' kind of setting for storage nodes will help me a lot (proposed implementation at #2124). Ticket #711 would also be useful. Also #1340 and [https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1212#comment:35 comment on #1212]
    26262. Repairing: Related to the above, I have to always ensure that no repair will end with all shares on the same node. So before doing a repair between 2 nodes I ensure that each isolated node is 100% repaired (10/10) and all files healthy. Then I 'prune' the storage shares to 5 and now is when I can do a 2 node verify/repair. I know this is very inefficient, so any advice on how to improve this is welcome.
    27273. Verification: I would like to place in each node crontab to do a deep-check-verify of the root verifycap and currently I can't because of #568. So I keep an eye on it.