<div></div><div>Hi, all,</div><div></div><div>I'm new to gluster, but found it interesting. I want to setup gluster in a way to be similar with HDFS.</div><div></div><div>There is my sample vol-file:</div><div></div><div>
volume posix<br> type storage/posix<br> option directory /data1/gluster<br>end-volume<br><br>volume locks<br> type features/locks<br> subvolumes posix<br>end-volume<br><br>volume brick<br> type performance/io-threads<br>
subvolumes locks<br>end-volume<br><br>volume server<br> type protocol/server<br> option transport-type tcp<br> option auth.addr.brick.allow *<br> subvolumes brick<br>end-volume<br><br>volume compute-5-0<br> type protocol/client<br>
option transport-type tcp<br> option remote-host compute-5-0<br> option remote-subvolume brick<br>end-volume<br><br>volume compute-5-1<br> type protocol/client<br> option transport-type tcp<br> option remote-host compute-5-1<br>
option remote-subvolume brick<br>end-volume<br><br>volume compute-5-2<br> type protocol/client<br> option transport-type tcp<br> option remote-host compute-5-2<br> option remote-subvolume brick<br>end-volume<br><br>volume compute-5-3<br>
type protocol/client<br> option transport-type tcp<br> option remote-host compute-5-3<br> option remote-subvolume brick<br>end-volume<br><br>volume compute-5-4<br> type protocol/client<br> option transport-type tcp<br> option remote-host compute-5-4<br>
option remote-subvolume brick-ns<br>end-volume<br><br>volume primary<br> type cluster/replicate<br> option local-volume-name primary <br> subvolumes compute-5-0 compute-5-1<br>end-volume<br><br>volume secondary<br> type cluster/replicate<br>
option local-volume-name secondary <br> subvolumes compute-5-2 compute-5-3<br>end-volume<br><br>volume unified<br> type cluster/unify<br> option scheduler rr<br> option local-volume-name unified # do I need this?<br>
option namespace compute-5-4 # do I need this?<br> subvolumes primary secondary<br>end-volume<br><br>volume writebehind<br> type performance/write-behind<br> option cache-size 1MB<br> subvolumes unified<br>end-volume<br>
<br>volume cache<br> type performance/io-cache<br> option cache-size 512MB<br> subvolumes writebehind<br>end-volume<br><br></div><div>The glusterd is up & running and no error msg in the logs. However, it reports some error when I tried to mount it:</div>
<div>[2009-07-01 09:37:36] E [xlator.c:736:xlator_init_rec] xlator: Initialization of volume 'fuse' failed, review your volfile again<br>[2009-07-01 09:37:36] E [glusterfsd.c:498:_xlator_graph_init] glusterfs: initializing translator failed<br>
[2009-07-01 09:37:36] E [glusterfsd.c:1191:main] glusterfs: translator initialization failed. exiting<br><br></div><div>I guess it is a very common question. Anyone has any idea?</div><div></div><div>BR,</div><div>Gnep</div>
<div></div><div></div>