v1.2.4

Fixes

• Fix the issue that Pump & Drainer has different node id between tidb-ansible and TiUP (#903, @lucklove)
  • For the cluster imported from tidb-ansible, if the pump or drainer is restarted, it will start with a new node id
  • Risk of this issue: binlog may not work correctly after restart pump or drainer
• Fix the issue that audit log may get lost in some special case (#879, #882, @9547)
  • If the user execute two commands one follows the other, and the second one quit in 1 second, the audit log of the first command will be overwirten by the second one
  • Risk caused by this issue: some audit logs may get lost in above case
• Fix the issue that new component deployed with tiup cluster scale-out doesn't auto start when rebooting (#905, @9547)
  • Risk caused by this issue: the cluster may be unavailable after rebooting
• Fix the issue that data directory of tiflash is not deleted if multiple data directories are specified (#871, @9547)
• Fix the issue that node_exporter and blackbox_exporter not cleaned up after scale-in all instances on specified host (#857, @9547)
• Fix the issue that the patch command will fail when try to patch dm cluster (#884, @lucklove)
• Fix the issue that the bench component report Error 1105: client has multi-statement capability disabled (#887, @mahjonp)
• Fix the issue that the TiSpark node can't be upgraded (#901, @lucklove)
• Fix the issue that tiup-playground can't start TiFlash with newest nightly PD (#902, @lucklove)

Improvements

• Ignore no tispark master error when listing clusters since the master node may be remove by scale-in --force (#920, @AstroProfundis)