Question

G.1.1.

On a Tungsten Replicator Replica, how do I set both the local Replica THL listener port and the upstream Primaries THL listener port?

Answer 1

You need to specify two options: thl-port to set the Replica THL listener port and master-thl-port to define the upstream Primary THL listener port. Otherwise thl-port alone sets BOTH.

Answer 2

To update the IP address used by one or more hosts in your cluster, you must perform the following steps:

If possible, switch the node into SHUNNED mode.
Reconfigure the IP address on the machine.
Update the hostname lookup, for example, by editing the IP configuration in /etc/hosts.
Restart the networking to reconfigure the service.
On the node that has changed IP address, run the following from the software staging directory:
```
shell> tools/tpm update --replace-release
```
On all other nodes within the cluster:
1. Update the hostname lookup for the new node, for example, by updating the IP configuration in /etc/hosts.
2. Place the cluster into MAINTENANCE mode.
3. Execute the following from the software staging directory:
```
shell> tools/tpm update --replace-release
```

Answer 3

If you need to change the password used by Tungsten Cluster to connect to a dataserver and apply changes, the password can be updated first by changing the information within the your dataserver, and then by updating the configuration using tpm update. The new password is not checked until the Tungsten Replicator process is starting. Changing the password and then updating the configuration will keep replication from failing.

Within cctrl set the MAINTENANCE policy mode:
```
cctrl> set policy maintenance
```
Within MySQL, update the password for the user, allowing the change to be replicated to the other datasources:
```
mysql> SET PASSWORD FOR tungsten@'%' = PASSWORD('new_pass');
```
Update the values for datasource-password=new_pass in your /etc/tungsten/tungsten.ini and issue tpm update
Set the policy mode in cctrl back to AUTOMATIC :
```
cctrl> set policy automatic
```

Answer 4

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:

shell> ntpdate pool.ntp.org

Once the command has been executed across all the hosts, trying sending a heartbeat on the Primary to Replicas and checking the latency:

shell> trepctl heartbeat

Answer 5

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 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.

Answer 6

You can change the configuration by adding/adjusting the following property in the /etc/tungsten/tungsten.ini and then issuing tpm update

java-mem-size=2048

Answer 7

The use of triggers can cause many issues with replication, and the effects can differ between different binlog-format settings (Such as ROW vs STATEMENT)

For a full explanation see Section C.4.1, “Triggers”

G.1.1.	On a Tungsten Replicator Replica, how do I set both the local Replica THL listener port and the upstream Primaries THL listener port?
	You need to specify two options: `thl-port` to set the Replica THL listener port and `master-thl-port` to define the upstream Primary THL listener port. Otherwise `thl-port` alone sets BOTH.
G.1.2.	How do I update the IP address of one or more hosts in the cluster?
	To update the IP address used by one or more hosts in your cluster, you must perform the following steps: If possible, switch the node into SHUNNED mode. Reconfigure the IP address on the machine. Update the hostname lookup, for example, by editing the IP configuration in `/etc/hosts`. Restart the networking to reconfigure the service. On the node that has changed IP address, run the following from the software staging directory: shell> `tools/tpm update --replace-release` On all other nodes within the cluster: Update the hostname lookup for the new node, for example, by updating the IP configuration in `/etc/hosts`. Place the cluster into `MAINTENANCE` mode. Execute the following from the software staging directory: shell> `tools/tpm update --replace-release`
G.1.3.	How do I update the password for the replication user in the cluster?
	If you need to change the password used by Tungsten Cluster to connect to a dataserver and apply changes, the password can be updated first by changing the information within the your dataserver, and then by updating the configuration using tpm update. The new password is not checked until the Tungsten Replicator process is starting. Changing the password and then updating the configuration will keep replication from failing. Within cctrl set the `MAINTENANCE` policy mode: cctrl> `set policy maintenance` Within MySQL, update the password for the user, allowing the change to be replicated to the other datasources: mysql> `SET PASSWORD FOR tungsten@'%' = PASSWORD('new_pass');` Update the values for `datasource-password=new_pass` in your `/etc/tungsten/tungsten.ini` and issue tpm update Set the policy mode in cctrl back to `AUTOMATIC` : cctrl> `set policy automatic`
G.1.4.	One of my hosts is regularly a number of seconds behind my other Replicas?
	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: shell> `ntpdate pool.ntp.org` Once the command has been executed across all the hosts, trying sending a heartbeat on the Primary to Replicas and checking the latency: shell> `trepctl heartbeat`
G.1.5.	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 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.
G.1.6.	How do you change the replicator heap size after installation?
	You can change the configuration by adding/adjusting the following property in the `/etc/tungsten/tungsten.ini` and then issuing tpm update java-mem-size=2048
G.1.7.	What effect do triggers have on replication, either row or statement-based?
	The use of triggers can cause many issues with replication, and the effects can differ between different binlog-format settings (Such as ROW vs STATEMENT) For a full explanation see Section C.4.1, “Triggers”

Prev	Up	Next
Appendix G. Frequently Asked Questions (FAQ)	^Level	G.2. Cloud Deployment and Management

Continuent Documentation

G.1. General Questions