text: Release 6.1.1 contains both significant improvements as well as some needed bugfixes.
  A new feature called "Cluster State Savepoints" has been implemented.
  This new functionality was created to support clean, consistent rollbacks during aborted switch and failover operations. This functionality works for both physical clusters as well as for composite clusters.
  To support this new feature, a new cluster sub-command has been added to the cctrl command - cluster topology validate, which will check and validate a cluster topology and, in the process, will report any issues that it finds. The purpose of this command is to provide a fast way to see, immediately, if there are any issues with any components of a cluster.
  Savepoints are created automatically with every switch and failover command. The savepoint is only used if there is an exception during switch or failover that is actually able to be rolled-back.
  Not all exceptions during switch and failover will cause a rollback.
  In particular, if an exception happens during switch or failover AFTER a new primary datasource has been put online (relay or Primary) then the switch or failover operation cannot be rolled back.
  The Manager is configured, by default, to hold a maximum of 50 savepoints. When that limit is hit, the Manager resets the current-savepoint-id to 0 and starts to overwrite existing savepoints, starting at 0.
  Issues: CT-951
  For more information, see The cctrl Command.
  Fixed an issue where the ls resources command run inside of cctrl would fail to list the MANAGER entry on a Replica node.
  Issues: CT-599
  If the pipeline source replicator goes OFFLINE, the relay will reconnect to a different Replica.
  Issues: CT-871
  Tungsten Clustering 6.1.1 Includes the following changes made in Tungsten Replicator 6.1.1
  Added Clickhouse applier support.
  Issues: CT-383
  If using the dropcolumn filter during extraction, in conjunction with the Batch Applier (eg Replicating to Redshift, Hadoop, Vertica) writes would fail with a CSV mismatch error due to gaps in the THL Index.
  However, for JDBC appliers, the gaps are required to ensure the correct column mapping
  To handle the two different requirements, a new property has been added to the filter to control whether or not to leave the THL index untouched (the default) or to re-order the Index ID's
  If applying to Batch targets, then the following property should be added to your configuration. The property is not required for JDBC targets.
  --property=replicator.filter.dropcolumn.fillGaps=true
  Issues: CT-1025
  Fixed an issue that would prevent reading remote binary logs when using SSL.
  Issues: CT-958
  Fixed an issue where the command trepctl -all-services status -name watches fails.
  Issues: CT-977
  Restored previously-removed log file symbolic links under $CONTINUENT_ROOT/service_logs/
  Issues: CT-1026
  Fixed a bug where tpm diag would generate an empty zip file if the hostnames contain hyphens (-) or periods (.)
  Issues: CT-1032
  Improve ability to find needed binaries for commands: tungsten_find_position, tungsten_find_seqno and tungsten_get_rtt
  Issues: CT-1054
  1.17. Tungsten Clustering 6.1.2 GA (20 January 2020) ^Level 1.19. Tungsten Clustering 6.1.0 GA (31 July 2019)