One of my hosts is regularly a number of seconds behind my other slaves?
The most likely culprit for this issue is that the time is different on the machine in question. If you have ntp or a similar network time tool installed on your machine, use it to update the current time across all the hosts within your deployment:
Once the command has been executed across all the hosts, trying sending a heartbeat on the master to slaves and checking the latency:
Does the replicate filter (i.e. replicate.do and replicate.ignore) address both DML and DDL?
Both filters replicate.do and replicate.ignore will either do or ignore both DML and DDL
DDL is currently ONLY replicated for MySQL to MySQL or Oracle to Oracle topologies, or within MySQL Clusters, although it would be advisable not to use ignore/do filters in a clustered environment where data/structural integrity is key.
With replicate.do, all DML and DDL will be replicated ONLY for any database or table listed as part of the do filter.
With replicate.ignore, all DML and DDL will be replicated except for any database or table listed as part of the ignore filter.
How do you change the replicator heap size after installation?
You can change the configuration by running the following command from the staging directory:
On a Tungsten Replicator slave, how do I set both the local slave THL listener port and the upstream master's THL listener port?