-
Posts
52 -
Joined
-
Last visited
Posts posted by firstimpression
-
-
Hi,
We have a distributed installation (replicated MySQL database, maintenance-distributed running, etc). What is the correct procedure to upgrade version of Revive on such system?
Are the upgrade scripts aware that they run on a delivery node or on master server?
From what I understand, the moment I upgrade master node, the upgrade wizard will make changes to database that will make delivery node think that the system is already upgraded, wouldn't it?
Upgrade Of Revive In Distributed Environment
in Managing Revive Adserver
Posted
Please tell me if this is the correct thing to do:
1 Upload new files to master node, enter upgrade wizard on master node.
2 Do all the upgrade procedure. Changes that will have to be made in replicated tables will also be made on delivery node.
3 Upload new files to delivery node. Go to upgrade wizard on delivery mode.
4 The wizard will be aware that version is old on this machine. It will try to do the same changes to tables.
5 On some tables on delivery node the changes will be made again (because of replication some changes are already there). Disregarding that, I have to stop MySQL on master node, create a dump, check current binary log index, import dump to delivery node, and execute "CHANGE MASTER TO ..." with the correct index position?