Tungsten Replicator 6.1.19
Build: 22
Release Date: 17 Oct 2022
End of Life Date: 15 Aug 2024
Product End of Life
This release is past End of Life.
Behavior Changes (2)
The following changes 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:
Command-line Tools (1)
- The
check_tungsten.shwas deprecated in release 6.1.18 and has now been removed from this release.Issue: CT-1939
Core Replicator (1)
repl-svc-extractor-multi-frag-service-detectionis now turned **ON** by default. Event shards are determined at extraction time. With fragmented events, the shard cannot be determined by only reading the first fragment, but needs to check the last fragment as well. With this setting turned OFF, there is no issue with pipelines that don't need it, i.e. no parallel apply downstream replicas. However, as this is done at extract time, THL contains this information, and adding or changing a replica using parallel apply could introduce issues.NoteIt can be disabled if you see a performance overhead but this should be done with caution. For Aurora<>Aurora Active/Active deployments it is essential that this property be left ON.Issue: CT-1959
Improvements, new features and functionality (3)
Command-line Tools (3)
- The
tpm askcommand has five new variables available:dsrole&dsstatefor the current datasource, andtrrole&trstatefor the current replicator, andnodeinfowhich displays all 4 of the new variables.Issue: CT-1944 - The
tpm ask stagesandtpm ask allstagescommands have been added to display the Replicator stages for the current node (stages) and the stages for each role (allstages).Issue: CT-1943 - The
tpmcommand calls toglobhave been improved to be more strict and compliant.Issue: CT-1940
Bug Fixes (7)
Installation and Deployment (1)
- The
tpm installandtpm updatecommands now properly support thethl-portoption for cross-site subservices.Issue: CT-1953
Command-line Tools (2)
- The
tpm mysqlcommand will now gracefully handle being run on a non-database node.Issue: CT-1946 - Fixes an issue where the pause state would be badly displayed under no load, when the pause reaches the defined time. Note this is only a display issue : once an event is received, the pause state and displayed remaining time will be reset correctly.Issue: CT-1942
Core Replicator (3)
- Fixed an issue where the replicator would hang after applying a
DROP TABLEevent, that originally failed on the primary, but got logged into the binlog.Issue: CT-1973 - Fixed an issue where the
shard_idstored in the trep_commit_seqno table would show an incorrect shard after processing a skipped event (an event from another channel)Issue: CT-1967 - Fixes an issue that would leave a transaction uncommitted longer than necessary.Issue: CT-1958
Filters (1)
- The
BidiRemoteSlaveFiltercould fail to correctly flag fragmented events in unprivileged environments (Aurora, for example) In such an environment (multi-active, unprivileged database access), a new setting was introduced to force extraction process to read ahead to the last fragment to detect the service name (false by default). Enabled withrepl-svc-extractor-multi-frag-service-detection=trueIssue: CT-1351