diff --git a/FAQ.md b/FAQ.md index 6f8830b..01036e2 100644 --- a/FAQ.md +++ b/FAQ.md @@ -167,8 +167,7 @@ Also,assuming at least some of your nodes are on same LAN and others are widely And total number of nodes is not too big. And all your nodes under your control(at least - they are VPSes/Servers which are in your/friends you trust to pay in time name).And - if some storage nodes are permanently down - you can reconfigure gateways you use manually and run repair. Please note, it's much better to have nodes with roughly same space(500Gb and 5Gb in same grid is not a good idea,if you for some odd reason must have them both - read and think again,if you still think you must - don't count them in S in below calculations) -Let's say S=number_of_nodes), setup k=3,N=S,h=N-2, -use N=number_of_nodes_total, h=N-2 +Let's say S=number_of_nodes), setup k=3,N=S,h=N-2, use N=number_of_nodes_total, h=N-2 following links can also be helpful: @@ -177,5 +176,4 @@ following links can also be helpful: **Q25: Is there a process or command to make shares spread to new storage servers?** -A: -No. Not yet. ;) Such a process will probably be implemented and there is a ticket ([#232](https://tahoe-lafs.org/trac/tahoe-lafs/ticket/232), [#1657](https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1657), [#699](https://tahoe-lafs.org/trac/tahoe-lafs/ticket/699), [#661](https://tahoe-lafs.org/trac/tahoe-lafs/ticket/661), [#543](https://tahoe-lafs.org/trac/tahoe-lafs/ticket/543)) for it. +A: This is called "rebalancing". It isn't currently implemented, but the repair function can accomplish a similar result sometimes. Repair of immutables will upload shares to servers if necessary to reach "servers-of-happiness", which sometimes has the desired effect of uploading shares to newly added servers. Repair of mutables never uploads new shares. Here are tickets about improving rebalancing behavior: #232, #1657, #699, #661, #543. \ No newline at end of file