Skip to content

Latest commit

 

History

History
635 lines (461 loc) · 59.5 KB

CHANGELOG.md

File metadata and controls

635 lines (461 loc) · 59.5 KB
Raw

TiUP Changelog

[1.8.2] 2022-01-11

Fixes

  • Fix global configuration not inherited correctly in scale-out command of tiup-cluster (#1701, @srstack)
  • Fix errors starting tiup-playground in some circumstances (#1712 #1715, @nexustar)
  • Fix error comparing nightly versions in tiup-cluster (#1702, @srstack)

Improvements

[1.8.1] 2021-12-20

Fixes

  • Fix port conflict not checked for TiDB clusters imported from tidb-ansible on scale-out in tiup-cluster (#1656, @srstack)
  • Fix SSH commands stale in some circumstances (#1664, @nexustar)
  • Fix default value of initial-commit-ts for drainer in tiup-cluster (#1678, @nexustar)

Improvements

  • Display check result of CPU frequency governor even when it's not available (#1663, @srstack)

[1.8.0] 2021-12-06

New Features

  • Add data-dir support for TiCDC in tiup-playground (#1631, @nexustar)
  • Add support of using custom files as input of edit-config, and support dumping the current full config to a file with show-config command in tiup-cluster (#1637, @haiboumich)
  • Add support of next-generation monitor (ng-monitor) in tiup-playground (#1648, @nexustar)
  • Add support of inserting custom scrape_configs to Prometheus configs in tiup-cluster (#1641, @nexustar)
  • [experimental] Support 2-staged scaling out for tiup-cluster (#1638 #1642, @srstack)
    • Scaling out of a TiDB cluster can be devided with --stage1 and --stage2 arguments, the stage 1 deploys files and configs but not starting the new instances, and the stage 2 actually starts the new instances and reload necessary configs
    • This could be useful if you want to modify config of the new instances or use a custom binary with patch before the first start of the new instances
  • [experimental] Implement plain text output and support custom output writer for logs (#1646, @AstroProfundis)

Fixes

  • Fix incorrect progress bar displaying in some tasks (#1624, @nexustar)
  • Fix incorrect argument flags in tiup-playground (#1635, @srstack)
  • Fix files of monitoring agents and TiDB audit log not cleaned with clean command of tiup-cluster (#1643 #1644, @srstack)
  • Fix confirmation prompt in scale-out can not be skipped with --yes argument in tiup-cluster (#1645, @srstack)
  • Fix directory conflict error in some circumstances even when node is marked as ignore_exporter (#1649, @AstroProfundis)
  • Fix DM nodes not added to node_exporter target list in Prometheus config in tiup-dm (#1654, @AstroProfundis)

Improvements

  • Add significant warning when --force argument is set for scale-in command in tiup-cluster (#1629, @AstroProfundis)
  • Add environment variables to skip topology sanity check in scale-in command in tiup-cluster (#1627, @AstroProfundis)
  • Update examples to use --without-monitor instead of --monitor for tiup-playground (#1639, @dveeden)

[1.7.0] 2021-11-15

New Features

  • Support deploying and managing TLS enabled TiDB cluster with TiFlash nodes (#1594, @nexustar)
  • Support rendering template for local deployment with vairables in tiup-cluster and tiup-dm (#1596, @makocchi-git)
  • [experimental] Support optionally enable next-generation monitor (ng-monitor) for latest TiDB releases (#1601, @nexustar)
  • [experimental] Support JSON output format for tiup-cluster and tiup-dm (#1617, @AstroProfundis)

Fixes

Improvements

[1.6.1] 2021-10-21

Fixes

[1.6.0] 2021-10-09

New Features

  • Add support of using ssh-agent auth socket in tiup-cluster (#1416, @9547)
  • Add parallel task concurrency control in tiup-cluster and tiup-dm with -c/--concurrency argument (#1420, @AstroProfundis)
    • The default value of max number of parallel tasks allowed is 5, this feature could help users managing very large clusters to avoid connection errors on operations.
  • Add the ability to detect CPU arch for deployment servers automatically in tiup-cluster and tiup-dm if not set by user (#1423, @9547)
  • Add renew subcommand for tiup mirror to extend the expiration date of component manifest (#1479, @AstroProfundis)
  • Add the ability to ignore monitor agents for specific instances in tiup-cluster (#1492, @AstroProfundis)
  • Add --force argument for prune subcommand in tiup-cluster (#1552, @AstroProfundis)
  • Add more configuration fields for Grafana in tiup-cluster and tiup-dm (#1566, @haiboumich)
  • [Experimental] Add support of SSH connections via proxy in tiup-cluster (#1438, @9547)
  • Deprecate the --monitor argument and introduce a new --without-monitor argument to disable monitoring components in tiup-playground (#1512, @LittleFall)
  • Deprecate the TIUP_WORK_DIR environment as it's not actually been used, and make it possible for tiup-playground to run without tiup (#1553 #1556 #1558, @nexustar)

Fixes

  • Fix blackbox_exporter configs for TLS enabled clusters in tiup-cluster (#1443, @9547)
  • Only try to apply THP fix if it's available on the deployment server in tiup-cluster (#1458, @9547)
  • Fix sudo errors in tiup-cluster when devtoolset is enabled on deployment server (#1516, @nexustar)
  • Fix test cases for tiup-dm (#1540, @nexustar)
  • Fix downloading of uneeded component packages when --binpath is specifiedin tiup-playground (#1495, @AstroProfundis; #1545, @nexustar)
  • Fix panic when tiup-bench fails to connect to the database (#1557, @nexustar)
  • Fix numa_node configs are not rendered into PD startup script in tiup-cluster (#1565, @onlyacat)
  • Correctly handle -- in command line arguments passed to tiup (#1569, @dveeden)

Improvements

[1.5.6] 2021-09-01

Fixes

  • Fix OS version check rules for tiup-cluster check (#1535, @AstroProfundis)
  • Fix component upgrade order for tiup-cluster to make sure TiCDC nodes work correctly (#1542, @overvenus)

Improvements

  • Adjust warning message of tiup-cluster restart to make users clear that the cluster will be unavailable during the process (#1523, @glkappe)
  • Reverse the order of audit log listing to show latest records at the buttom (#1538, @AstroProfundis)

[1.5.5] 2021-08-19

Fixes

  • Fix error when reloading a stopped cluster with --skip-restart argument (#1513, @AstroProfundis)
  • Use absolute path for sudo command, to workaround errors on systems where devtoolset is enabled (#1516, @nexustar)
  • Fix custom TiDB port not correctly set in playground (#1511, @hecomlilong)

Improvements

  • Adjust suggested argument order in playground examples (#1522, @glkappe)

[1.5.4] 2021-08-05

Fixes

Improvements

[1.5.3] 2021-07-15

Fixes

  • Fix incorrect alert rules for TiDB version 3.x (#1463, @9547)
  • Fix TiKV config check to correctly handle the data_dir value (#1471, @tabokie)

Improvements

  • Update dependencies and adjust error message of ctl (#1459, @AstroProfundis)
  • Use $SHELL environment variable for completion (#1455, @dveeden)
  • Allow listing components from local cached manifests without network access (#1466, @c4pt0r)
  • Adjust error message of SELinux check failure (#1476, @AstroProfundis)
  • Adjust warning message when scale-in with --force argument to make it more clear of potential risks (#1477, @AstroProfundis)

[1.5.2] 2021-06-24

Fixes

  • Fix native SSH not working with custom SSH port (#1424, @9547)
  • Fix dashboard address displaying issue for tikv-slim clusters (#1428, @iosmanthus)
  • Fix a typo in help message of tiup-playground (#1429, @ekexium)
  • Fix TiFlash nodes not handled correctly in some commands (#1431, @lucklove)
  • Fix jemalloc config for TiKV nodes (#1435, @9547)
  • Fix the issue that slow log is not placed under log_dir (#1441, @lucklove)

Improvements

[1.5.1] 2021-06-11

Fix

[1.5.0] 2021-06-09

New Features

  • Show more information in display subcommand of tiup-cluster
    • Add an --uptime argument to show time since the last state change of process (#1231, @9547)
    • Show deploy user in display output and adjust formats (#1390 #1409, @AstroProfundis)
  • Add JSON output for display subcommand of tiup-cluster (#1358, @dveeden)
  • Add double confirmation for scale-out subcommand in tiup-cluster to let users be aware of global configs being used (#1309, @AstroProfundis)
  • Support deploying pure TiKV cluster with --mode tikv-slim in playground (#1333, @iosmanthus; #1365, @tisonkun)
  • Support data dir settings for TiCDC in tiup-cluster (#1372, @JinLingChristopher)
  • Support change of GCTTL and TZ configs for TiCDC in tiup-cluster (#1380, @amyangfei)
  • Add a local deployment template for tiup-cluster (#1404, @kolbe)
  • Support using dot (.) in cluster name (#1412, @9547)

Fixes

  • Fix a variety of typos (#1306, @kolbe)
  • Fix non-common speed units shown in downloading progress (#1312, @dveeden)
  • Fix the issue that it may panic when user try to list expired component (#1391, @lucklove)
  • Fix the issue that tikv not upgraded on error increasing schedule limit (#1401, @AstroProfundis)

Improvements

[1.4.4] 2021.05.26

Fixes

  • Fix the issue that upgrade process may fail if the PD node is not available for longer than normal after restart (#1359, @AstroProfundis)
  • Fix incorrect MALLOC_CONF value for TiKV node, set prof_active to false (#1361 #1369, @YangKeao)
    • Risk of this issue: Generating prof data for TiKV node with prof_active=true may cause high CPU systime usage in some circumstances, users need to regenerate startup scripts for TiKV nodes with tiup cluster reload <cluster-name> -R tikv to make the update applied
  • Fix the issue that the global log_dir not generated correctly for absolute paths (#1376, @lucklove)
  • Fix the issue that display command may report label mismatch warning if placement-rule is enabled (#1378, @lucklove)
  • Fix the issue that SELinux setting is incorrect when tiup-cluster tries to disable it with check --apply (#1383, @AstroProfundis)
  • Fix the issue that when scaling out instance on a host imported from tidb-ansible, the process may report error about monitor directory conflict (#1386, @lucklove)

Improvements

[1.4.3] 2021.05.13

Fixes

Improvements

[1.4.2] 2021.04.26

Fixes

  • Send meta output from tiup to stderr to not to mix with output of components (#1298, @dveeden)
  • Update confusing version selection examples in help message of playground (#1318, @AstroProfundis)
  • Fix the issue that tiup mirror clone command does exclude yanked component correctly (#1321, @lucklove)

Improvements

[1.4.1] 2021.04.07

Fixes

  • Fix pprof failing for TiKV in playground (#1272, @hicqu)
  • Fix the issue that TiFlash node may be failed to restart in playground (#1280, @lucklove)
  • Fix the issue that binlog_enable is not imported from tidb-ansible correctly (#1261, @lucklove)
  • Fix directory conflict check error for TiDB and DM clusters imported from ansible deployment (#1273, @lucklove)
  • Fix compatibility issue during upgrade for PD v3.x (#1274, @lucklove)
  • Fix failure of parsing very long audit log in replay for tiup-cluster (#1259, @lucklove)
  • Fix log dir path of Grafana for tiup-cluster (#1276, @rkazak)
  • Fix config check error when the cluster was deployed with an legacy nightly version in tiup-cluster (#1281, @AstroProfundis)
  • Fix error when using nightly version while the actual component is not available in repo (#1294, @lucklove)

Improvements

  • Refine PD scaling script rendering to optimize the code (#1253, @9547)
  • Start PD and DM master nodes sequentially in (#1262, @9547)
  • Properly follow the ignore config check argument in reload for tiup-cluster (#1265, @9547)

[1.4.0] 2021.03.31

New Features

  • EXPERIMENTAL: Add support of Apple M1 devices (#1122, @terasum @AstroProfundis @sunxiaoguang)
    • Playground may not fully work as some components don't yet have packages for darwin-arm64 released
  • Not displaying dashboard address if it's "none" or "auto" (#1054, @9547)
  • Support filtering nodes and roles in check subcommand of tiup-cluster (#1030, @AstroProfundis)
  • Support retry of failed operations from where it broke with replay command of tiup-cluster and tiup-dm (#1069 #1157, @lucklove)
  • Support upgrade and patch a stopped TiDB / DM cluster (#1096, @lucklove)
  • Support setting global custom values for topology of tiup-cluster (#1098, @lucklove)
  • Support custom root_url and anonymous login for Grafana in tiup-cluster (#1085, @mianhk)
  • Support remote read and remote write for Prometheus node in tiup-cluster (#1070, @XSHui)
  • Support custom external AlertManager target for Prometheus node in tiup-cluster (#1149, @lucklove)
  • Support force reinstallation of already installed component (#1145, @9547)
  • Add --force and retain data options to tiup-dm (#1080, @9547)
  • Add enable/disable subcommands to tiup-dm (#1114, @9547)
  • Add template subcommand to tiup-cluster to print pre-defined topology templates (#1156, @lucklove)
  • Add --version option to display subcommand of tiup-cluster to print the cluster version (#1207, @AstroProfundis)
  • Allow value type change when editing topology with edit-config subcommand of tiup-cluster (#1050, @AstroProfundis)

Fixes

  • Not allowing deployment if the input topology file is empty (#994, @AstroProfundis)
  • Fix data dir setting for Prometheus (#1040, @9547)
  • Fix the issue that pre-defined Prometheus rules may be missing if a custom rule_dir is set (#1073, @9547)
  • Fix the issue that config files of Prometheus and Grafana are not checked before start (#1074, @9547)
  • Fix the issue that cluster name is not validated for some operations (#1177, @AstroProfundis)
  • Fix the issue that tiup-cluster reloads a cluster even if the config may contain errors (#1183, @9547)
  • Fix the issue that publish command may fail when uploading files without retry (#1174 #1202, @AstroProfundis; #1167, @lucklove)
  • Fix the issue that newly added TiFlash nodes may fail to start during scale-out in tiup-cluster (#1227, @9547)
  • Fix incorrect cluster name in alert messages (#1238, @9547)
  • Fix the issue that blackbox_exporter may not collecting ping metrics correctly (#1250, @STRRL)

Improvements

[1.3.7] 2021.03.25

Fixes

  • Fix the issue that metrics of tiflash-server instance may not collected correctly (#1083, @yuzhibotao)
  • Fix the issue that tiup-cluster disables monitoring services unexpectedly (#1088, @lucklove)
  • Fix wrong dashboard name for lightning in Grafana after renaming a cluster with tiup-cluster (#1196, @9547)
  • Fix the issue that tiup-cluster prune command may try to generate config for removed nodes (#1237, @lucklove)

[1.3.6] 2021.03.19

Fixes

  • Fix the issue that can't deploy arm64 binary with offline mirror (#1229, @lucklove)

[1.3.5] 2021.03.11

Fixes

[1.3.4] 2021.03.05

Fixes

  • Fix the issue that tiup-cluster can't gernerate prometheus config (#1185, @lucklove)
  • Fix the issue that tiup may choose yanked version if it's already installed (#1191, @lucklove)

[1.3.3] 2021.03.04

Fixes

  • Fix the issue that tiup will hang forever when reloading a stopped cluster (#1044, @9547)
  • Fix the issue that tiup mirror merge does not work on official offline package (#1121, @lucklove)
  • Fix the issue that there may be no retry when download component failed (#1137, @lucklove)
  • Fix the issue that PD dashboard does not report grafana address in playground (#1142, @9547)
  • Fix the issue that the default selected version may be a preprelease version (#1128, @lucklove)
  • Fix the issue that the error message is confusing when the patched tar is not correct (#1175, @lucklove)

Improvements

  • Add darwin-arm64 not support hint in install script (#1123, @terasum)
  • Improve playground welcome information for connecting TiDB (#1133, @dveeden)
  • Bind latest stable grafana and prometheus in DM deploying (#1129, @lucklove)
  • Use the advertised host instead of 0.0.0.0 for tiup-playground (#1152, @9547)
  • Check tarball checksum on tiup-server when publish component (#1163, @lucklove)

[1.3.2] 2021.01.29

Fixes

  • Fix the issue that the grafana and alertmanager target not set in prometheus.yaml (#1041, @9547)
  • Fix the issue that grafana deployed by tiup-dm missing home.json (#1056, @lucklove)
  • Fix the issue that the expires of cloned mirror is shourened after publish component to it (#1051, @lucklove)
  • Fix the issue that tiup-cluster may remove wrong paths for imported cluster on scale-in (#1068, @AstroProfundis)
    • Risk of this issue: If an imported cluster has deploy dir ending with /, and sub dirs as <deploy-dir>//sub, it could results to delete wrong paths on scale-in
  • Fix the issue that imported *_exporter has wrong binary path (#1101, @AstroProfundis)

Improvements

  • Apply more strict check on tar.gz file for patch command: check if the entry is an executable file (#1091, @lucklove)

[1.3.1] 2020.12.31

Fixes

  • Workaround the issue that store IDs in PDs may not monotonically assigned (#1011, @AstroProfundis)
    • Currently, the ID allocator is guaranteed not to allocate duplicated IDs, but when PD leader changes multiple times, the IDs may not be monotonic
    • For tiup < v1.2.1, the command tiup cluster display may delete store (without confirm) by mistake due to this issue (high risk)
    • For tiup >= v1.2.1 and <= v1.3.0, the command tiup cluster display may display up stores as tombstone, and encourages the user to delete them with the command tiup cluster prune (medium risk)
  • Fix the issue that the cluster check always fail on thp check even though the thp is disabled (#1005, @lucklove)
  • Fix the issue that the command tiup mirror merge -h outputs wrong usage (#1008, @lucklove)
    • The syntax of this command should be tiup mirror merge <mirror-dir-1> [mirror-dir-N] but it outputs tiup mirror merge <base> <mirror-dir-1> [mirror-dir-N]
  • Fix the issue that prometheus doesn't collect drainer metrics (#1012, @SE-Bin)

Improvements

  • Reduce display duration when PD nodes encounter network problems and droping packages (#986, @9547)
  • cluster, dm: support version input without leading 'v' (#1009, @AstroProfundis)
  • Add a warning to explain that we will stop the cluster before clean logs (#1029, @lucklove)
    • When a user try to clean logs with the command tiup cluster clean --logs, he may expect that the cluster is still running during the clean operation
    • The actual situation is not what he expect, which may suprise the user (risk)

[1.3.0] 2020.12.17

New Features

  • Modify TiFlash's query memory limit from 10GB to 0(unlimited) in playground cluster (#907, @LittleFall)
  • Import configuration into topology meta when migrating a cluster from Ansible (#766, @yuzhibotao)
    • Before, we stored imported ansible config in ansible-imported-configs which is hidden for users, in this release, we merge the configs into meta.yaml so that the user can see the config with the command tiup cluster edit
  • Enhance the tiup mirror command (#860, @lucklove)
    • Support merge two or more mirrors into one
    • Support publish component to local mirror besides remote mirror
    • Support add component owner to local mirror
  • Partially support deploy cluster with hostname besides ip address (EXPERIMENTAL) (#948,#949, @fln)
    • Not usable for production, as there would be issue if a hostname resolves to a new IP address after deployment
  • Support setting custom timeout for waiting instances up in playground-cluster (#968, @unbyte)
  • Support check and disable THP in tiup cluster check (#964, @anywhy)
  • Support sign remote manifest and rotate root.json (#967, @lucklove)

Fixes

  • Fixed the issue that the public key created by TiUP was not removed after the cluster was destroyed (#910, @9547)
  • Fix the issue that user defined grafana username and password not imported from tidb-ansible cluster correctly (#937, @AstroProfundis)
  • Fix the issue that playground cluster not quiting components with correct order: TiDB -> TiKV -> PD (#933, @unbyte)
  • Fix the issue that TiKV reports wrong advertise address when --status-addr is set to a wildcard address like 0.0.0.0 (#951, @lucklove)
  • Fix the issue that Prometheus doesn't reload target after scale-in action (#958, @9547)
  • Fix the issue that the config file for TiFlash missing in playground cluster (#969, @unbyte)
  • Fix Tilfash startup failed without stderr output when numa is enabled but numactl cannot be found (#984, @lucklove)
  • Fix the issue that the deployment environment fail to copy config file when zsh is configured (#982, @9547)

Improvements

  • Enable memory buddyinfo monitoring on node_exporter to collect exposes statistics of memory fragments (#904, @9547)
  • Move error logs dumped by tiup-dm and tiup-cluster to ${TIUP_HOME}/logs (#908, @9547)
  • Allow run pure TiKV (without TiDB) cluster in playground cluster (#926, @sticnarf)
  • Add confirm stage for upgrade action (#963, @Win-Man)
  • Omit debug log from console output in tiup-cluster (#977, @AstroProfundis)
  • Prompt list of paths to be deleted before processing in the clean action of tiup-cluster (#981, #993, @AstroProfundis)
  • Make error message of monitor port conflict more readable (#966, @JaySon-Huang)

[1.2.5] 2020.11.27

Fixes

  • Fix the issue that can't operate the cluster which have tispark workers without tispark master (#924, @AstroProfundis)
    • Root cause: once the tispark master been removed from the cluster, any later action will be reject by TiUP
    • Fix: make it possible for broken clusters to fix no tispark master error by scaling out a new tispark master node
  • Fix the issue that it report pump node id not found while drainer node id not found (#925, @lucklove)

Improvements

  • Support deploy TiFlash on multi-disks with "storage" configurations since v4.0.9 (#931, #938, @JaySon-Huang)
  • Check duplicated pd_servers.name in the topology before truly deploy the cluster (#922, @anywhy)

[1.2.4] 2020.11.19

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 playground cluster 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)

[1.2.3] 2020.10.30

Fixes

  • Fix misleading warning message in the display command (#869, @lucklove)

[1.2.1] 2020.10.23

Improvements

  • Introduce a more safe way to cleanup tombstone nodes (#858, @lucklove)
    • When an user scale-in a TiKV server, it's data is not deleted until the user executes a display command, it's risky because there is no choice for user to confirm
    • We have add a prune command for the cleanup stage, the display command will not cleanup tombstone instance any more
  • Skip auto-start the cluster before the scale-out action because there may be some damaged instance that can't be started (#848, @lucklove)
    • In this version, the user should make sure the cluster is working correctly by themselves before executing scale-out
  • Introduce a more graceful way to check TiKV labels (#843, @lucklove)
    • Before this change, we check TiKV labels from the config files of TiKV and PD servers, however, servers imported from tidb-ansible deployment don't store latest labels in local config, this causes inaccurate label information
    • After this we will fetch PD and TiKV labels with PD api in display command

Fixes

  • Fix the issue that there is datarace when concurrent save the same file (#836, @9547)
    • We found that while the cluster deployed with TLS supported, the ca.crt file was saved multi times in parallel, this may lead to the ca.crt file to be left empty
    • The influence of this issue is that the tiup client may not communicate with the cluster
  • Fix the issue that files copied by TiUP may have different mode with origin files (#844, @lucklove)
  • Fix the issue that the tiup script not updated after scale-in PD (#824, @9547)

[1.2.0] 2020.09.29

New Features

Fixes

  • Fix tiup update --self results to tiup's binary file deleted (#816, @lucklove)
  • Fix per-host custom port for drainer not handled correctly on importing (#806, @AstroProfundis)
  • Fix the issue that help message is inconsistent (#758, @9547)
  • Fix the issue that dm not applying config files correctly (#810, @lucklove)
  • Fix the issue that playground display wrong TiDB number in error message (#821, @SwanSpouse)

Improvements

  • Automaticlly check if TiKV's label is set (#800, @lucklove)
  • Download component with stream mode to avoid memory explosion (#755, @9547)
  • Save and display absolute path for deploy directory, data dirctory and log directory to avoid confusion (#822, @lucklove)
  • Redirect DM stdout to log files (#815, @csuzhangxc)
  • Skip download nightly package when it exists (#793, @lucklove)

[1.1.2] 2020.09.11

Fixes

  • Fix the issue that TiKV store leader count is not correct (#762)
  • Fix the issue that TiFlash's data is not clean up (#768)
  • Fix the issue that tiup cluster deploy --help display wrong help message (#758)
  • Fix the issue that tiup-playground can't display and scale (#749)

[1.1.1] 2020.09.01

Fixes

  • Remove the username root in sudo command #731
  • Transfer the default alertmanager.yml if the local config file not specified #735
  • Only remove corresponed config files in InitConfig for monitor service in case it's a shared directory #736

[1.1.0] 2020.08.28

New Features

  • [experimental] Support specifying customized configuration files for monitor components (#712, @lucklove)
  • Support specifying user group or skipping creating a user in the deploy and scale-out stage (#678, @lucklove)
  • [experimental] Support rename cluster by the command tiup cluster rename <old-name> <new-name> (#671, @lucklove)

    Grafana stores some data related to cluster name to its grafana.db. The rename action will NOT delete them. So there may be some useless panel need to be deleted manually.

  • [experimental] Introduce tiup cluster clean command (#644, @lucklove):
    • Cleanup all data in specified cluster: tiup cluster clean ${cluster-name} --data
    • Cleanup all logs in specified cluster: tiup cluster clean ${cluster-name} --log
    • Cleanup all logs and data in specified cluster: tiup cluster clean ${cluster-name} --all
    • Cleanup all logs and data in specified cluster, excepting the Prometheus service: tiup cluster clean ${cluster-name} --all --ignore-role Prometheus
    • Cleanup all logs and data in specified cluster, expecting the node 172.16.13.11:9000: tiup cluster clean ${cluster-name} --all --ignore-node 172.16.13.11:9000
    • Cleanup all logs and data in specified cluster, expecting the host 172.16.13.11: tiup cluster clean ${cluster-name} --all --ignore-node 172.16.13.12
  • Support skipping evicting store when there is only 1 TiKV (#662, @lucklove)
  • Support importing clusters with binlog enabled (#652, @AstroProfundis)
  • Support yml source format with tiup-dm (#655, @july2993)
  • Support detecting port conflict of monitoring agents between different clusters (#623, @AstroProfundis)

Fixes

  • Set correct deploy_dir of monitoring agents when importing ansible deployed clusters (#704, @AstroProfundis)
  • Fix the issue that tiup update --self may make root.json invalid with offline mirror (#659, @lucklove)

Improvements

  • Add advertise-status-addr for TiFlash to support host name (#676, @birdstorm)

[1.0.9] 2020.08.03

tiup

  • Clone with yanked version #602
  • Support yank a single version on client side #602
  • Support bash and zsh completion #606
  • Handle yanked version when update components #635

tiup-cluster

  • Validate topology changes after edit-config #609
  • Allow continue editing when new topology has errors #624
  • Fix wrongly setted data_dir of TiFlash when import from ansible #612
  • Support native ssh client #615
  • Support refresh configuration only when reload #625
  • Apply config file on scaled pd server #627
  • Refresh monitor configs on reload #630
  • Support posix style argument for user flag #631
  • Fix PD config incompatible when retrieving dashboard address #638
  • Integrate tispark #531 #621