Indeed, it looks like you might be running into some DB connection issues that are causing other problems.
First, the root of everything is almost certainly that “DB timeout” error. You’re using ODBC to connect to SQL Server? While this is generally acceptable, the native driver (as in FactorySQL’s native driver, on the DB connection screen) has better performance, and I’d probably recommend it for things such as redundancy and sqltags. So, I would try to get a native driver connection set up pointing to the same DB, and then switch over redundancy to use that.
If it’s not possible, verify that connection pooling is enabled on the ODBC driver. Go to Windows’ ODBC configuration, go to the Connection Pooling tab, and then double click the driver that the DSN is using. Verify or enable connection pooling.
The “removed nodes” messages just mean that there were entries in the redundancy table that hadn’t been updated for some amount of time. When this happens, they are removed. The nodes re-insert their information, and a calculation is made as to who should be the master.
There are other potential causes of DB timeouts as well, such as table locking (if the server performs automatic backups/archiving) or just heavy load overall, but I would start by trying the native connection.