3.5.1 Matrix Server Upgrade Guide

Chapter 3: Double Rolling Upgrades 22

For example, the servers could have the following network interfaces:

server srv1: network interfaces 10.10.1.1 and 10.10.2.3

server srv2: network interfaces 10.10.1.2 and 10.10.2.2

server srv3: network interfaces 10.10.1.3 and 10.10.2.1

Run the command mx --numeric server status to determine the IP

addresses known to the matrix. In our example, the output is as follows

and indicates that srv3 (IP address 10.10.1.3) should be upgraded first.

10.10.1.1

10.10.1.2

10.10.1.3

NOTE: If a server is accidentally upgraded out of order, when a higher-

number server joins the matrix, the servers still running the old

version of Matrix Server will think they need to leave the matrix

and will no longer send configuration and status updates. To

correct this problem, stop Matrix Server on the node that was

upgraded out of order. Continue upgrading the other nodes

before starting Matrix Server on that node.

Other Considerations

• To ensure that applications can acquire fcntl(2) locks throughout the

upgrade, you will need to perform the rolling upgrade twice. The first

upgrade takes the servers to a supported operating system running

Matrix Server 3.5.1 in 32-bit mode. The second upgrade takes the

servers to 64-bit mode and allows Matrix Server to take advantage of

64-bit mode.

• During the rolling upgrade, the matrix will include a mix of servers

running 3.5.1 and the older release. As long as the matrix includes at

least one active server running the older release, other servers running

that release will be able to join the matrix (for example, following a

reboot). However, after the last server running the older release has

left the matrix, only servers running 3.5.1 can join the matrix.

Although Matrix Server supports a mix of servers running 3.5.1 and

the older release during the rolling upgrade, on-going operation of a