> http://www.gluster.org/docs/index.php/AFR_single_process So it means I cannot stop client / server role separately except I modify the volume spec file? I do not think it is acceptable for a productive environment. -----Original Message----- From: gluster-devel-bounces+kirbyzhou=sohu-rd.com@xxxxxxxxxx [mailto:gluster-devel-bounces+kirbyzhou=sohu-rd.com@xxxxxxxxxx] On Behalf Of Gordan Bobic Sent: Tuesday, February 03, 2009 7:42 PM To: gluster-devel@xxxxxxxxxx Subject: RE: Why integrate both client and server into a single executable? On Tue, 3 Feb 2009 19:29:53 +0800, Kirby Zhou <kirbyzhou@xxxxxxxxxxx> wrote: > I use RHEL-5.2 > What's your point of the distribution? 'NO_CONTENT_TYPE' problem or FUSE > problem? > The FUSE rpm does not come with RHEL, it should come from somewhere I do > not know now. I use RHEL5/CentOS5, too. I'm reasonably sure that fuse-libs are available in one of the core yum repositories, but I could be mistaken - I might have pulled them down from rpmforge or atrpms. > Do you mean you can set up both client and server in the same process? Yes. > How can I do it? Have a look here: http://www.gluster.org/docs/index.php/AFR_single_process The basic idea is that you have client and server blocks in the same config file. You can mount the volume spec as per normal client setup, but the process will also act as a server because that was also specified in the volume spec file. > Is it a new feature in the 2.0rc1? No, it's been around for a while. > However I do not think it is always a good idea, the server role is much > more stable than the client role. If you mix the 2, you would lost the > stability. Theoretically, yes. In practice, I've found that it doesn't make any difference. If your use-case is tripping a bug, it'll do so consistently, so you'll end up with the whole setup stopping working anyway. Gordan _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxx http://lists.nongnu.org/mailman/listinfo/gluster-devel
