[tahoe-dev] A simple 2 nodes replication
David-Sarah Hopwood
david-sarah at jacaranda.org
Fri Feb 15 03:31:11 UTC 2013
On 14/02/13 14:15, Paul Rabahy wrote:
> I believe that you need to set .happy to 1. With happy set to 1, it will still try to
> upload a share to both nodes, but it consider the upload a success as long as 1 share
> uploaded successfully. I have found that in practice, both shares will end up on the node
> that is online (when one is offline).
>
> Once the second node comes back online, you should run "tahoe check --repair" to improve
> the redundancy of the shares that were uploaded while a node was offline. Please verify
> this, I am a little unclear on if --repair just does a repair (regenerate missing shares),
> or also does a rebalance (move shares from node to node to improve redundancy).
Unfortunately, --repair does not rebalance. This is
<https://tahoe-lafs.org/trac/tahoe-lafs/ticket/699>, which I just added to the
1.11 milestone.
--
David-Sarah Hopwood ⚥
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 555 bytes
Desc: OpenPGP digital signature
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20130215/925fe56d/attachment.pgp>
More information about the tahoe-dev
mailing list