On 11 October 2016 at 22:32, Jackie Tung wrote:
> Joe,
>
> Thanks for that, that was educational. Gluster docs claim that since 3.7,
> DHT hash ranges are weighted based on brick sizes by default:
>
> $ gluster volume get Option Value
>
> --
Joe,
Thanks for that, that was educational. Gluster docs claim that since 3.7, DHT
hash ranges are weighted based on brick sizes by default:
$ gluster volume get =11 are 8TB, subvolume <= 10 is are 6TB.
Do you think it is possible to even out usage on all bricks by % utilized now?
This would
I've written an example of how gluster's dht works on my blog at
https://joejulian.name/blog/dht-misses-are-expensive/ which might make
it clear why the end result is not what you expected.
By setting cluster.min-free-disk (defaults to 10%) you can, at least,
ensure that your new bricks are ut
Hi,
We have a 2 node, distributed replicated setup (11 bricks on each node). Each
of these bricks are 6TB in size.
node_A:/brick1 replicates node_B:/brick1
node_A:/brick2 replicates node_B:/brick2
node_A:/brick3 replicates node_B:/brick3
…
…
node_A:/brick11 replicates node_B:/brick11
We recent