6.11.2.1. Installing Cassandra Replication (Staging Method)

Configuration of the replication deployment to Cassandra can be made using a single tpm staging-based deployment. However, because the configuration must be different for the master and slave hosts, the configuration must be performed in multiple steps.

  1. Unpack the Tungsten Replicator distribution in staging directory:

    shell> tar zxf tungsten-replicator-tungsten-replicator-5.3.4-606.tar.gz
  2. Change into the staging directory:

    shell> cd tungsten-replicator-tungsten-replicator-5.3.4-606
  3. Configure the main parameters for the replicator service:

    shell> ./tools/tpm configure alpha \
    --batch-enabled=true \
    --batch-load-language=js \
    --batch-load-template=cassandra \
    --datasource-type=file \
    --install-directory=/opt/continuent \
    --master=ubuntuheterosrc \
    --members=cassandra \
    --property=replicator.datasource.applier.csvType=cassandra \
    --property=replicator.datasource.global.csvType=cassandra \
    --property=replicator.stage.q-to-dbms.blockCommitInterval=5s \
    --property=replicator.stage.q-to-dbms.blockCommitRowCount=1000 \
    --replication-password=secret \
    --replication-user=tungsten \
    --rmi-port=25550 \
    --skip-validation-check=DatasourceDBPort \
    --skip-validation-check=DirectDatasourceDBPort \
    --skip-validation-check=HostsFileCheck \
    --skip-validation-check=InstallerMasterSlaveCheck \
    --skip-validation-check=ReplicationServicePipelines \
    --start-and-report=true \
    --svc-applier-filters=dropstatementdata

    The description of each of the options is shown below; click the icon to hide this detail:

    Click the icon to show a detailed description of each argument.

  4. Install the services:

    shell> ./tools/tpm install

If you encounter problems during the installation, check the output of the /tmp/tungsten-configure.log file for more information about the root cause.

Once the service is configured and running, the service can be monitored as normal using the trepctl command. See Section 6.11.3, “Management and Monitoring of Cassandra Deployments” for more information.