1.4

l In the Scheduling Preferences of the Slave, both "Maximum Records" are ignored.
Scheduling is handled by the Master.
l The "Expected Remote Merge Engine" and "Expected Remote Weaver Engine" in Merge
Engine Scheduling and Weaver Engine Scheduling respectively, on the Master, should
each equal the total number of engines in all the slaves combined.
l
For example, the Expected Remote Merge Engine on the Master should equal the
total of "Local Engines Launched" for each slave.
l
If the number of expected remote engines is lower than the actual number,
performance will not be optimal.
l
If the number of expected remote engines is higher than the actual number, jobs
may fail and not complete.
l Cleanup Service requires special configuration on Clustering setups:
l Cleanup service should not run simultaneously on all machines (staggered
cleanup). Doing so may cause jobs not to be processed since all servers are busy.
l Only the machine where the MySQL Server product is installed should attempt to
cleanup database items. Essentially server that do not have MySQL should only run
Orphan File Cleanup.
Server Extension Scheduling Preferences
The Server Extension Scheduling Preferences define the connection settings for the server
extension (slave) and the main Server module (master).
l
Location of the master server: Enter the location and port of the main Server module in
the hostname:port format. For example, 192.168.100.123:9340 or connect-master:9340.
l
Username: Enter the username expected by the OLConnect Server.
l
Password: Enter the password expected by the OLConnect Server for the above
username.
l
Note that Maximum records in a small job and Minimum records in a large job:are
note used in Server Extensions. All server scheduling is handled by the Master.
Page 40