One idea , docs said that you should create new directory. Could you create a
new directory after add another server and copy files from old directory to new
one, then everything will be distributed.
I know that glusterfs do not have reallocation mechanism for distribute data to
new added bricks for achive performance and capcity problem.
*Now the question is what about adding a new server?
Currently hash works based on directory level distribution. i.e, a given
file's parent directory will have information of how the hash numbers are
mapped to subvolumes. So, adding new node doesn't disturb any current setup
as the files/dirs present already have its information preserved. Whatever new
directory gets created, will start considering new volume for scheduling files.
Regards
Vahric
-----Original Message-----
From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at
gluster.org] On Behalf Of Roland Rabben
Sent: Sunday, December 06, 2009 6:29 PM
To: gluster-users at gluster.org
Subject: [Gluster-users] Adding bricks to DHT
Hi
I have a GlusterFS DHT system that I need to expand in a few days. Reading up on
the documentation it seems to me that adding bricks won't solve our problem
because of how the hash works.
I have a fairly static folder structure, but the number of files are growing
fast. From what I understand, adding bricks will not allow new files to be
stored on the new bricks unless they are stored in new directories.
So my questions are:
1. How can I make sure the new bricks are used?
2. Is there a way to "rebalance" content over the new and old bricks?
I can't tolerate much downtime on my FS.
I am using GlusterFS 2.06.
Regards
Roland Rabben