So the same volume config file can be used to start up the server and
mount the FS?
i.e.
# glusterfsd -f /etc/glusterfs/foo.vol
and
/etc/glusterfs/foo.vol /foo glusterfs defaults 0 0
in /etc/fstab?
Or is an additional setup/option required somewhere?
Or is only one of the above actually required? Would in this
configuration mounting the FS get the server process going implicitly,
since it's now the same process?
Gordan
Amar S. Tumballi wrote:
Well,
I have completed a wiki page with example and few explanation here:
http://www.gluster.org/docs/index.php/Unify_NUFA_with_single_process
Though the example is for unify with nufa scheduler, it can be used for
any translators, like afr, stripe etc. (note: keep the order of
subvolume same in case of afr and stripe).
Regards,
Amar
On Tue, May 13, 2008 at 9:57 AM, Amar S. Tumballi <amar@xxxxxxxxxxxxx
<mailto:amar@xxxxxxxxxxxxx>> wrote:
I will be doing it today, and will reply back in this thread.
On Tue, May 13, 2008 at 9:55 AM, Dan Parsons <dparsons@xxxxxxxx
<mailto:dparsons@xxxxxxxx>> wrote:
Any luck on documenting this? I'd relaly like to set it up.
Dan Parsons
On May 10, 2008, at 1:10 PM, Anand Babu Periasamy wrote:
Hi Gordan,
"option transport-type unix/server" is available. Even
better approach is to
run in single address mode (server and client merged into
single process).
I will have Amar document it.
We are also introducing binary protocol and non-blocking
sockets in the
next release which will improve performance significantly.
--
Anand Babu Periasamy
GPG Key ID: 0x62E15A31
Blog [http://ab.freeshell.org]
The GNU Operating System [http://www.gnu.org]
Z RESEARCH Inc [http://www.zresearch.com]
Gordan Bobic wrote:
Is there a way to mount locally via a unix domain socket
rather than via loopback interface? It seems rather
wasteful to be passing all the traffic through the
TCP/IP stack for a local mount in cases when the server
is also a client for the shared mount.
i.e. is there something like "option transport-type
unix/client"?
Gordan
