We didn't mount multiple nodes to that file system and also the iSCSI channel is in a separate subnet. -----Original Message----- From: linux-cluster-bounces@xxxxxxxxxx [mailto:linux-cluster-bounces@xxxxxxxxxx] On Behalf Of Lon Hohberger Sent: Thursday, March 09, 2006 5:09 PM To: linux clustering Subject: RE: Cluster service restarting Locally On Thu, 2006-03-09 at 11:02 -0600, Hong Zheng wrote: > Lon, > > Thanks for your reply. In my system I don't use any lock system like > lock_gulm or lock_dlm, I use no_lock because our applications' > limitation. Do you think no_lock will also bring some lock traffic or > not? No, but if you mount the file system on more than one node, say "good bye" to your data. > When I tried lock_gulm before, our application had very bad > performance, so I choose no_lock. > > And I'm not sure which update we have right now. Do you know the > versions for clumanager and redhat-config-cluster of RHCS3U7? 1.2.28-1 is U6. U7 will be out soon. You can contact Red Hat Support if you want an earlier version. Another way to make things work a little better for you is to separate the cluster communication path from the iSCSI path so they're not contending for the same network. -- Lon -- Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster -- Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
