3.1.2 Matrix Server Administration Guide
Chapter 18: SAN Maintenance 238
Copyright © 1999-2006 PolyServe, Inc. All rights reserved.
Increase the Membership Partition Timeout
Under heavy I/O load, I/O timeouts can occur on membership partition
accesses, which can cause excessive I/O path switching. If you experience
this problem, increasing the membership partition timeout may resolve
the issue.
Before setting the timeout, be sure to stop Matrix Server.
To increase the timeout, edit the file /etc/opt/polyserve/mxinit.conf. Locate
the following line in the file:
# sanpulse_start_options = { "--mxinit" };
You will need to add the parameter "--mptimeout=<sec>" to the start
options. Also remove the comment character (#) from the beginning of
the line:
sanpulse_start_options = { "--mxinit","--mptimeout=<sec>" };
<sec> is the number of seconds (1-255) to be used as the I/O timeout for
accessing membership partitions. The default value is 5. Be sure to
increase the timeout period in small increments. If the timeout value is
too large, more time may be needed for filesystem recovery after a node
failure. The following example sets the timeout to 10 seconds:
sanpulse_start_options = { "--mxinit","--mptimeout=10" };
After adding the parameter, you can restart Matrix Server.
Repeat this procedure on each remaining server. You will also need to set
the timeout on any servers added to the matrix in the future.
Change the Fencing Method
This procedure describes how to change the matrix fencing method on
servers that are already running Matrix Server 3.1.
1. Stop Matrix Server on all servers in the matrix:
# /etc/init.d/pmxs stop
2. Reboot all servers having entries in the Matrix Server host registry.
Use this command to see a list of the affected servers:
# /opt/polyserve/lib/mpdump