Update: Clone Instances Download the JAR from the Admin Instance
No need to update the clone instances anymore.
One of the annoying and (usually) manual activities is updating every MockMotor clone instance when the admin instance is updated to a newer version.
The administrator needs to log into the admin box and update the admin.
./stopMockMotor.sh ./updateMockMotor.sh ./startMockMotor.sh
The administrator then has to log into every clone instance’s box, stop the instance, update it from the admin and start it again:
./stopMockMotor.sh ./updateMockMotorClone.sh ./startMockMotor.sh
If this is not done, the admin instance, to maintain the data integrity, rejects the clone merging into the cluster.
Now, it is enough to update only the admin instance. Then, when reporting their version to the restarted admin, clone instances receive the updated JAR from that admin and restart automatically with the new JAR version.
A small but satisfying improvement.