From 249b9f0ddfd642324b44152d85eb77ca0f34cc02 Mon Sep 17 00:00:00 2001 From: Ryan Brewster Date: Tue, 24 Apr 2018 14:55:41 -0700 Subject: [PATCH] Fix broken link in binary-deployment.md Caused by a capitalization mismatch --- op-guide/binary-deployment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/op-guide/binary-deployment.md b/op-guide/binary-deployment.md index 26578277e8799..43dc62b766fb0 100644 --- a/op-guide/binary-deployment.md +++ b/op-guide/binary-deployment.md @@ -323,7 +323,7 @@ Follow the steps below to start PD, TiKV, and TiDB: > **Note**: > > - If you start TiKV or deploy PD in the production environment, it is highly recommended to specify the path for the configuration file using the `--config` parameter. If the parameter is not set, TiKV or PD does not read the configuration file. -> - To tune TiKV, see [Performance Tuning for TiKV](./tune-TiKV.md). +> - To tune TiKV, see [Performance Tuning for TiKV](./tune-tikv.md). > - If you use `nohup` to start the cluster in the production environment, write the startup commands in a script and then run the script. If not, the `nohup` process might abort because it receives exceptions when the Shell command exits. For more information, see [The TiDB/TiKV/PD process aborts unexpectedly](../trouble-shooting.md#the-tidbtikvpd-process-aborts-unexpectedly). ## TiDB monitor and alarm deployment