[tahoe-dev] Storage Node Proactive Share Relocation

[Greg Troxel]

Nathan Eisenberg <nathan at atlasnetworks.us> writes:

> I got to wondering last night... say you have a grid that you're
> removing a storage node from for one reason or another.  In my mind,
> the current correct procedure would be to run a repair-walk through
> all the known DIRCAPs, to ensure everything is in a good state to
> start with, then stop the tahoe-LAFS storage node process, and run the
> repair walk again to regenerate the missing shares.

yes

> However, if you've got valid shares on that server, why not be able to
> use them to regenerate shares?  In other words, have the storage node
> reallocate its own shares before making them unavailable.

that's been discussed.  the notion would be to have the server place the
shares it has with some other servers.

The hard parts are:

  respecting the share distribution policies of the share owners

  dealing with accounting
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20110511/fa14a241/attachment.pgp>