Thank you for fast replay.
I am looking into GlusterFS to setup cluster of about 600 nodes with ~2TB local disk
per node. This is only possible, with our workloads, if data locality is somehow enforced,
so that data 'produced and consumed' by node stays on that node's local disk, because there is no
dedicated network infrastructure. Data availability in case of node failures is not of big concern.
Do you have any suggestions regarding glusterfs setup I can use?
Best Regards,
--
Gvozden Neskovic
neskovic@xxxxxxxxx
neskovic@xxxxxxxxx
On Tue, Mar 8, 2011 at 1:57 PM, Anand Babu Periasamy <ab@xxxxxxxxxxx> wrote:
Hi Gvozden, We have not tested switch translator in 3.1. Not enough interest around this translator as of now. My recommendation is to avoid this translator.
From: "Gvozden Neskovic" <neskovic@xxxxxxxxx>
To: gluster-devel@xxxxxxxxxx
Sent: Tuesday, March 8, 2011 4:51:00 AM
Subject: [Gluster-devel] Glusterfs 3.1.2 dht/switch_______________________________________________
Dear All,I observed random misbehaving and crashes on setup withswitch xlator on 20 nodes.Attached patch address following:memory leak in subvolume lookup,missing initialization in switch_create() andcorrect 'pattern.switch.case' option parsing.Best Regards.
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxx
http://lists.nongnu.org/mailman/listinfo/gluster-devel
