<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi,<br>
<br>
I've set up a 2 brick replicate system, using bonded GigE.<br>
<br>
eth0 - management<br>
eth1 & eth2 - bonded 192.168.20.x<br>
eth3 & eth4 - bonded 192.168.10.x<br>
<br>
I created the replicate over the 192.168.10 interfaces.<br>
<br>
<font face="Courier New, Courier, monospace"># gluster volume info<br>
<br>
Volume Name: raid5<br>
Type: Replicate<br>
Volume ID: 02b24ff0-e55c-4f92-afa5-731fd52d0e1a<br>
Status: Started<br>
Number of Bricks: 1 x 2 = 2<br>
Transport-type: tcp<br>
Bricks:<br>
Brick1: filer-1:/gluster-exported/raid5/data<br>
Brick2: filer-2:/gluster-exported/raid5/data<br>
Options Reconfigured:<br>
performance.nfs.stat-prefetch: on<br>
performance.nfs.io-cache: on<br>
performance.nfs.read-ahead: on<br>
performance.nfs.io-threads: on<br>
nfs.trusted-sync: on<br>
performance.cache-size: 13417728<br>
performance.io-thread-count: 64<br>
performance.write-behind-window-size: 4MB<br>
performance.io-cache: on<br>
performance.read-ahead: on<br>
</font><br>
<pre class="moz-signature" cols="72">I attached an NFS client across the 192.168.20 interface. The NFS works fine. Under load, though, I get 100% CPU usage of the nfs process and lose connectivity.
My plan was to replicate across the 192.168.10 bond as well as do gluster mounts. The NFS mount on 192.168.20 was to keep NFS traffic off the gluster link.
Is this a supported configuration? Does anyone else do this?
Gerald
--
Gerald Brandt
Majentis Technologies
<a class="moz-txt-link-abbreviated" href="mailto:gbr@majentis.com">gbr@majentis.com</a>
204-229-6595
<a class="moz-txt-link-abbreviated" href="http://www.majentis.com">www.majentis.com</a>
</pre>
</body>
</html>