B.1. Tungsten Replicator 5.0.0 Daily Builds (7 Dec 2015)

Behavior Changes

The following changes have been made to Tungsten Replicator and may affect existing scripts and integration tools. Any scripts or environment which make use of these tools should check and update for the new configuration:

  • The Bristlecone load generator toolkit is no longer included with Tungsten Replicator by default.

    Issues: CONT-903

  • The scripts previously located within the scripts directory have now been relocated to the standard bin directory. This does not affect their availability if the env.sh script has been used to update your path. This includes, but is not limited to, the following commands:

    • ebs_snapshot.sh

    • file_copy_snapshot.sh

    • multi_trepctl

    • tungsten_get_position

    • tungsten_provision_slave

    • tungsten_provision_thl

    • tungsten_read_master_events

    • tungsten_set_position

    • xtrabackup.sh

    • xtrabackup_to_slave

    Issues: CONT-904

  • The backup and restore functionality in trepctl has been deprecated and will be removed in a future release.

    Issues: CONT-906

  • The batch loading scripts used by HP Vertica, Hadoop and Amazon Redshift appliers have been moved to the appliers/batch directory.

    Issues: CONT-907

  • The location of the JavaScript filters has been moved to new location in keeping with the rest of the configuration:

    • samples/extensions/javascript has moved to support/filters-javascript

    • samples/scripts/javascript-advanced has moved to support/filters-javascript

    The use of these filters has not changed but the default location for some filter configuration files has moved to support/filters-config. Check your current configuration before upgrading.

    Issues: CONT-908

  • The ddlscan templates have been moved to the support/ddlscan directory.

    Issues: CONT-909

  • For compatibility with MySQL 5.7, the tpm command will now check for the super_read_only setting and warn if this setting is enabled.

    Issues: CONT-1039

  • For compatibility with MySQL 5.7, the tpm command will use the authentication_string field for validating passwords.

    Issues: CONT-1058

  • For compatibility with MySQL 5.7, the tpm command will now ignore the sys schema.

    Issues: CONT-1059

  • The Vertica applier should write exceptions to a temporary file during replication.

    The applier statements will include the EXCEPTIONS attribute in each statement to assist in debugging. Review the replicator log or trepctl status output for more details.

    Issues: CONT-1169

Known Issues

The following issues may affect the operation of Tungsten Replicator and should be taken into account when deploying or updating to this release.

  • Installation and Deployment

    • Under certain circumstances, the rsync process can randomly fail during the installation/ deployment process when using the staging method of deployment. The error code returned by rsync may be 12 or 23.

      The error is transient and non-specific and deployment should be retried.

      Issues: CONT-1343

  • Core Replicator

    • Use of LOAD DATA commands requires the correct permissions to be given to the mysql user. One of the following must be done.

      • The tungsten system user must have the same default group as the mysql system user.

      • The mysql system user must be a member of the default group for tungsten system user.

      • The --file-protection-level option must be set to none to allow full visibility to all temporary files.

    • The replicator can hit a MySQL lock wait timeout when processing large transactions.

      Issues: CONT-1106

    • The replicator can run into OutOfMemory when handling very large Row-Based replication events. This can be avoided by setting --optimize-row-events=false.

      Issues: CONT-1115

    • The replicator can fail during LOAD DATA commands or Vertica loading if the system permissions are not set correctly. If this is encountered, make sure the MySQL or Vertica system users are a member of the Tungsten system group. The issue may also be avoided by removing system file protections with --file-protection-level=none.

      Issues: CONT-1460

Improvements, new features and functionality

Bug Fixes

  • Core Replicator

    • A master replicator could fail to finish extracting a fragmented transaction if disconnected during processing.

      Issues: CONT-1163

    • A slave replicator could fail to come ONLINE if the last THL file is empty.

      Issues: CONT-1164

    • The replicator applier and filters may fail with ORA-955 because the replicator did not check for metadata tables using uppercase table names.

      Issues: CONT-1375

    • The replicator incorrectly assigns LOAD DATA statements to the #UNKNOWN shard. This can happen when the entire length is above 200 characters.

      Issues: CONT-1431