gluster-users-bounces at gluster.org wrote on 04/19/2011 11:07:09 AM: > I didn't title this well, so let me phrase that better. With 2-system > replicated mirror, there is a speed and reliability advantage in joining > those two systems with a crossover cable and putting those two nics in their > own private address space. Gluster-as-server is happy to do that. > > Gluster-as-client isn't happy in this arrangement, when the client is coming > in from the normal LAN addresses rather than the private addresses the > mirroring is using. This appears to be because the default behavior is for > the client to download the volume file from the servers, which then contains > the private IPs, which aren't available from the client's perspective. > > I knon in past versions of gluster the choice of the client downloading that > file, or having its own copy, was configurable. It's not clear from the > current stripped-down documentation whether that's still the case. Or if it > is, I don't find discussion of how to configure the client to work right in > this sort of setup. As it is, the client just hangs on the initial mount > request, and sits there consuming 100% of cpu until killed. Of course, > better behavior would be for the client to throw an error and quit in a > polite way - hanging at 100% cpu is just wrong. So... I've a very similar configuration, and while it is strongly discouraged by Gluster proper, we just place the configured client files on the machines and do it that way. -greg
