Skip to content

@shlomi-noach shlomi-noach released this Jun 22, 2020 · 185 commits to master since this release

Changes since v3.1.4: v3.1.4...v3.2.2

Notable changes:

core logic, detection & failover:

  • Support for FailMasterPromotionOnLagMinutes #1115
  • introducing gracefaul-master-takeover-auto: graceful takeover where orchestrator can auto-pick new master and also start replication on demoted master.
  • Better semi-sync analysis #1171, introducing NotEnoughValidSemiSyncReplicasStructureWarning
  • Analysis: locked semi sync master #1175, introducing LockedSemiSyncMaster

development, build & testing:


  • Orchestrator systemd depency #1112
  • Fixed ReadUnambiguousSuggestedClusterAliases logic #1161
  • fix mustPromoteOtherCoMaster debug message #1162
  • ascii topology: indicate errant GTID #1163
  • search recoveries by cluster alias #1090
  • skip AddReplicaKey if it is specified in config.Config.DiscoveryIgnoreReplicaHostnameFilters #1096
  • Support HTTPS for Consul KV #1047
  • Allow sorting clusters on dashboard by count, name, or alias #1054
  • Display region, data center, and environment in UI #1095
  • orchestrator-client: return raw JSON for api call on error #1166
  • Format delays in days / hours / minutes / seconds #1184
  • Skip Verify should be SSLSkipVerify Instead the mysql backend config. #1191


  • slave->replica changes throughout the code. #1168, #1182, #1187, #1188
  • API incompatibility: analysis names changes: DeadMasterAndSlaves->DeadMasterAndReplicas etc. See #1182
  • Web interface to use "replica" terminology (e.g. "Stop replication" button replaces "Stop slave")
  • API: transition into new terminology #1188:
    • The API for Instance now adds new terminology fields. Replicas is identical to SlaveHosts. ReplicaitonLagSeconds is identical to SlaveLagSeconds etc.
    • Users can opt to use the new naming convention. At this point I believe there is no user interaction (command line, API call, parsing API response) that forces the user to use slave terminology.
    • There is no plan at this time for deprecating old names.
    • Internally, the old names have been removed, and are only exposed in the API for backwards compatibility.

Contributions by @jhriggs, @luisyonaldo, @rluisr, @smirnov-vs, @MaxFedotov, @sjmudd, @cezmunsta , @mcrauwel , @pospelov-v, @martinarrieta - thank you!

$ sha256sum *
b7fe2069db0092041d8ec3a427efb8a072773de9c8648962885ad35d4a38b67b  orchestrator-3.2.2-1.x86_64.rpm
e90fa66a37c8d509e7d4b1c3a4118fd8c8bc8d8b856fa183ddadf31f11a1f3f7  orchestrator_3.2.2_amd64.deb
334c6f01e05abf428d62625001f0371d117944cf92d12da49bc6ae958501e6e4  orchestrator-3.2.2-linux-amd64.tar.gz
c7e05ca9b8493e93caedc77a1e39daacf2071f9827166fe296b4b1f93e7075f5  orchestrator-cli-3.2.2-1.x86_64.rpm
f351e8cac721eea7fa8786954e53f8d514f3673497d017d133a58e38e17a7657  orchestrator-cli_3.2.2_amd64.deb
ba15f1a2070ffc710f74e25c756d38f82732ea450bed59507b8fc5bfb231b864  orchestrator-client-3.2.2-1.x86_64.rpm
ac6606ca10fb644315d5f88baa262611cea5136d16e4dcf38f886eee3ee7c854  orchestrator-client_3.2.2_amd64.deb
b9a381dd64ab218ac87635e6367d51b88629eb5b416b4bce1e5db68121685642  orchestrator-client-sysv-3.2.2-1.x86_64.rpm
89ef1d3fd9b4476bdb9da92fbceb4321c1cb010573c694836b71336e7ca98d42  orchestrator-client-sysv-3.2.2_amd64.deb
6294ea0f6b16c8ed0715eb8ba92edfbd9e2326c7b6da7073e296f175a62e0c09  orchestrator-cli-sysv-3.2.2-1.x86_64.rpm
3d9dd1b0fdcd20688c8c49088a4a11c312af0eaa0d907454e721d8b0cf9a2068  orchestrator-cli-sysv-3.2.2_amd64.deb
a907a53ab0d630c89b290672ef9c2fbdb5fd06d75b89fe94291e20fff4c515fc  orchestrator-sysv-3.2.2-1.x86_64.rpm
ab42fad5833efe2d3d737c5dd8fa687188ad007cb63eb6aab060967222da7ddc  orchestrator-sysv-3.2.2_amd64.deb
Assets 15