| Option | --security-directory | |
| Config File Options | security-directory | |
| Description | Storage directory for the Java security/encryption files | |
| Value Type | string | |
| Option | --service-alias | |
| Aliases | --dataservice-service-alias | |
| Config File Options | dataservice-service-alias, service-alias | |
| Description | Replication alias of this dataservice | |
| Value Type | string | |
| Option | --service-name | |
| Config File Options | service-name | |
| Description | Set the service name | |
Set the service name
| Option | --service-type | |
| Aliases | --repl-service-type | |
| Config File Options | repl-service-type, service-type | |
| Description | What is the replication service type? | |
| Value Type | string | |
| Valid Values | local | |
| remote | ||
| Option | --skip-statemap | |
| Config File Options | skip-statemap | |
| Description | Do not copy the cluster-home/conf/statemap.properties from the previous install | |
| Value Type | boolean | |
| Option | --slaves | |
| Aliases | --dataservice-slaves, --members | |
| Config File Options | dataservice-slaves, members, slaves | |
| Description | What are the Replicas for this dataservice? | |
| Value Type | string | |
| Option | --start | |
| Config File Options | start | |
| Description | Start the services after configuration | |
| Value Type | string | |
| Option | --start-and-report | |
| Config File Options | start-and-report | |
| Description | Start the services and report out the status after configuration | |
| Value Type | string | |
--svc-allow-any-remote-service
| Option | --svc-allow-any-remote-service | |
| Aliases | --repl-svc-allow-any-remote-service | |
| Config File Options | repl-svc-allow-any-remote-service, svc-allow-any-remote-service | |
| Description | Replicate from any service | |
| Value Type | boolean | |
| Default | false | |
| Valid Values | true | |
--svc-applier-block-commit-interval
| Option | --svc-applier-block-commit-interval | |
| Aliases | --repl-svc-applier-block-commit-interval | |
| Config File Options | repl-svc-applier-block-commit-interval, svc-applier-block-commit-interval | |
| Description | Minimum interval between commits | |
| Value Type | string | |
| Valid Values | 0 | When batch service is not enabled |
| #d | Number of days | |
| #h | Number of hours | |
| #m | Number of minutes | |
| #s | Number of seconds | |
--svc-applier-block-commit-size
| Option | --svc-applier-block-commit-size | |
| Aliases | --repl-svc-applier-block-commit-size | |
| Config File Options | repl-svc-applier-block-commit-size, svc-applier-block-commit-size | |
| Description | Applier block commit size (min 1) | |
| Value Type | numeric | |
| Option | --svc-applier-filters | |
| Aliases | --repl-svc-applier-filters | |
| Config File Options | repl-svc-applier-filters, svc-applier-filters | |
| Description | Replication service applier filters | |
| Value Type | string | |
--svc-applier-last-applied-write-interval
| Option | --svc-applier-last-applied-write-interval | |
| Config File Options | svc-applier-last-applied-write-interval | |
| Description | Interval (in seconds) to store the last known applied seqno and latency | |
| Value Type | string | |
| Option | --svc-extractor-filters | |
| Aliases | --repl-svc-extractor-filters | |
| Config File Options | repl-svc-extractor-filters, svc-extractor-filters | |
| Description | Replication service extractor filters | |
| Value Type | string | |
| Option | --svc-fail-on-zero-row-update | |
| Aliases | --repl-svc-fail-on-zero-row-update | |
| Config File Options | repl-svc-fail-on-zero-row-update, svc-fail-on-zero-row-update | |
| Description | How should the replicator behave when a Row-Based Replication UPDATE or DELETE does not affect any rows. | |
| Value Type | string | |
| Default | stop | |
| Valid Values | ignore | No warnings in the log file, and replication continues |
| warn | Log a Warning in the log file, but continue anyway | |
From release 7.0.1 the default for this property was changed to stop, previously, the default was warn.
The change in the default value may cause unexpected behavior in Active/Active topologies due to the
Asynchronous nature of replication, however care should be taken if changing back to the original default
of warn.
If you notice many entries in your replicator logs indicating zero row updates, and these warnings are being ignored, you may encounter data drift.
| Option | --svc-parallelization-type | |
| Aliases | --repl-svc-parallelization-type | |
| Config File Options | repl-svc-parallelization-type, svc-parallelization-type | |
| Description | Method for implementing parallel apply | |
| Value Type | string | |
| Valid Values | disk | |
| memory | ||
| none | ||
| Option | --svc-remote-filters | |
| Aliases | --repl-svc-remote-filters | |
| Config File Options | repl-svc-remote-filters, svc-remote-filters | |
| Description | Replication service remote download filters | |
| Value Type | string | |
--svc-reposition-on-source-id-change
| Option | --svc-reposition-on-source-id-change | |
| Aliases | --repl-svc-reposition-on-source-id-change | |
| Config File Options | repl-svc-reposition-on-source-id-change, svc-reposition-on-source-id-change | |
| Description | The Primary will come ONLINE from the current position if the stored source_id does not match the value in the static properties | |
| Value Type | string | |
| Option | --svc-shard-default-db | |
| Aliases | --repl-svc-shard-default-db | |
| Config File Options | repl-svc-shard-default-db, svc-shard-default-db | |
| Description | Mode for setting the shard ID from the default db | |
| Value Type | string | |
| Valid Values | relaxed | |
| stringent | ||
--svc-systemd-config-connector
| Option | --svc-systemd-config-connector | |
| Config File Options | svc-systemd-config-connector | |
| Description | Used to provide custom systemd configuration that will be used in place of the default generated on. | |
| Value Type | string | |
This property can be used to supply an alternative, custom, systemd configuration that will be used in place of the default generated one.
The value of the parameter should be specified as the name and location of the custom script to use instead, for example:
svc-systemd-config-connector=/home/tungsten/connector.service
Where connector.service file could look something like the following:
[Unit] Description=Tungsten Connector After=mysqld.service mysql.service mariadb.service tmanager.service treplictor.service [Service] User=tungsten Type=forking ExecStart=/opt/continuent/tungsten/tungsten-connector/bin/connector start sysd ExecStop=/opt/continuent/tungsten/tungsten-connector/bin/connector stop sysd ExecStartPre=/opt/my-pre-start-script.sh [Install] WantedBy=multi-user.target
| Option | --svc-systemd-config-manager | |
| Config File Options | svc-systemd-config-manager | |
| Description | Used to provide custom systemd configuration that will be used in place of the default generated on. | |
| Value Type | string | |
This property can be used to supply an alternative, custom, systemd configuration that will be used in place of the default generated one.
The value of the parameter should be specified as the name and location of the custom script to use instead, for example:
svc-systemd-config-manager=/home/tungsten/manager.service
Where manager.service file could look something like the following:
[Unit] Description=Tungsten Manager After=mysqld.service mysql.service mariadb.service treplicator.service [Service] User=tungsten Type=forking ExecStart=/opt/continuent/tungsten/tungsten-manager/bin/manager start sysd ExecStop=/opt/continuent/tungsten/tungsten-manager/bin/manager stop sysd ExecStartPre=/opt/my-pre-start-script.sh [Install] WantedBy=multi-user.target
--svc-systemd-config-replicator
| Option | --svc-systemd-config-replicator | |
| Config File Options | svc-systemd-config-replicator | |
| Description | Used to provide custom systemd configuration that will be used in place of the default generated on. | |
| Value Type | string | |
This property can be used to supply an alternative, custom, systemd configuration that will be used in place of the default generated one.
The value of the parameter should be specified as the name and location of the custom script to use instead, for example:
svc-systemd-config-replicator=/home/tungsten/replicator.service
Where replicator.service file could look something like the following:
[Unit] Description=Tungsten Replicator After=mysqld.service mysql.service mariadb.service [Service] User=tungsten Type=forking ExecStart=/opt/continuent/tungsten/tungsten-replicator/bin/replicator start sysd ExecStop=/opt/continuent/tungsten/tungsten-replicator/bin/replicator stop sysd ExecStartPre=/opt/my-pre-start-script.sh [Install] WantedBy=multi-user.target
| Option | --svc-table-engine | |
| Aliases | --repl-svc-table-engine | |
| Config File Options | repl-svc-table-engine, svc-table-engine | |
| Description | Replication service table engine | |
| Value Type | string | |
| Default | innodb | |
| Option | --svc-thl-filters | |
| Aliases | --repl-svc-thl-filters | |
| Config File Options | repl-svc-thl-filters, svc-thl-filters | |
| Description | Replication service THL filters | |
| Value Type | string | |