Peng Zhao wrote:
Hi, all,
I'm new to gluster, but found it interesting. I want to setup gluster in a way to be similar with HDFS.
There is my sample vol-file:
volume posix
 type storage/posix
 option directory /data1/gluster
end-volume

volume locks
  type features/locks
  subvolumes posix
end-volume

volume brick
 type performance/io-threads
 subvolumes locks
end-volume

volume server
 type protocol/server
 option transport-type tcp
 option auth.addr.brick.allow *
 subvolumes brick
end-volume

volume compute-5-0
 type protocol/client
 option transport-type tcp
 option remote-host compute-5-0
 option remote-subvolume brick
end-volume

volume compute-5-1
 type protocol/client
 option transport-type tcp
 option remote-host compute-5-1
 option remote-subvolume brick
end-volume

volume compute-5-2
 type protocol/client
 option transport-type tcp
 option remote-host compute-5-2
 option remote-subvolume brick
end-volume

volume compute-5-3
 type protocol/client
 option transport-type tcp
 option remote-host compute-5-3
 option remote-subvolume brick
end-volume

volume compute-5-4
 type protocol/client
 option transport-type tcp
 option remote-host compute-5-4
 option remote-subvolume brick-ns
end-volume

volume primary
 type cluster/replicate
 option local-volume-name primary
 subvolumes compute-5-0 compute-5-1
end-volume

volume secondary
 type cluster/replicate
 option local-volume-name secondary
 subvolumes compute-5-2 compute-5-3
end-volume

volume unified
 type cluster/unify
 option scheduler rr
 option local-volume-name unified          # do I need this?
 option namespace compute-5-4           # do I need this?
 subvolumes primary secondary
end-volume

volume writebehind
  type performance/write-behind
  option cache-size 1MB
  subvolumes unified
end-volume

volume cache
  type performance/io-cache
  option cache-size 512MB
  subvolumes writebehind
end-volume

The glusterd is up & running and no error msg in the logs. However, it reports some error when I tried to mount it: [2009-07-01 09:37:36] E [xlator.c:736:xlator_init_rec] xlator: Initialization of volume 'fuse' failed, review your volfile again [2009-07-01 09:37:36] E [glusterfsd.c:498:_xlator_graph_init] glusterfs: initializing translator failed [2009-07-01 09:37:36] E [glusterfsd.c:1191:main] glusterfs: translator initialization failed. exiting

I guess it is a very common question. Anyone has any idea?
BR,

Try generating the log file with log-level set to bug. You
can do so by using the "-L DEBUG" command line parameter.

The debug log level will give us a better idea of what
exactly is failing.

-Shehjar
Gnep


------------------------------------------------------------------------

_______________________________________________
Gluster-users mailing list
Gluster-users@gluster.org
http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users


_______________________________________________
Gluster-users mailing list
Gluster-users@gluster.org
http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users

Reply via email to