5.7.2. Installing Vertica Replication

Configuration of the replication deployment to Vertica 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-5.0.tar.gz
  2. Change into the staging directory:

    shell> cd tungsten-replicator-5.0
  3. Locate the Vertica JDBC driver. This can be downloaded separately from the Vertica website. The driver will need to be copied into the Tungsten Replicator lib directory.

    shell> cp vertica-jdbc-7.1.2-0.jar tungsten-replicator-5.0.0-0/tungsten-replicator/lib/
  4. Configure the main parameters for the replicator service:

    shell> ./tools/tpm configure alpha \
        --master=host1 \
        --members=host1,host3 \
        --install-directory=/opt/continuent \
        --disable-relay-logs=true \
        --skip-validation-check=HostsFileCheck \
        --enable-heterogeneous-service=true \
        --start

    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.

  5. Configure the parameters for the master host which will extract the information from MySQL:

    shell> ./tools/tpm configure alpha \
        --hosts=host1 \
        --replication-user=tungsten \
        --replication-password=password \
        --enable-heterogeneous-master=true 

    This operation sets the user and password information for accessing the MySQL server; this is required by some of the filters which extract information from the running service.

    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.

  6. Configure the parameters for the slave host that will apply the events to Vertica:

    shell> ./tools/tpm configure alpha \
        --hosts=host3 \
        --replication-user=dbadmin \
        --replication-password=password \
        --batch-load-template=vertica \
        --batch-load-language=js \
        --datasource-type=vertica \
        --vertica-dbname=bigdata \
        --replication-host=host3 \
        --replication-port=5433 \
        --skip-validation-check=InstallerMasterSlaveCheck \
        --svc-applier-block-commit-size=25000 \
        --svc-applier-block-commit-interval=30s

    This configure the Vertica slave to accept replication data from the master.

    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.

  7. Install the services:

    shell> ./tools/tpm install

Once 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 5.7.3, “Management and Monitoring of Vertica Deployments” for more information.