tools: update whitespace (pingcap#378)

Author: lilin90

tools/tidb-binlog-kafka.md

@@ -15,7 +15,7 @@ TiDB-Binlog supports the following scenarios:
 
 - **Data synchronization**: to synchronize TiDB cluster data to other databases  
 - **Real-time backup and recovery**: to back up TiDB cluster data, and recover in case of cluster outages
-  
+
 ## TiDB-Binlog architecture
 
 The TiDB-Binlog architecture is as follows:
@@ -47,7 +47,7 @@ The Kafka cluster stores the binlog data written by Pump and provides the binlog
 wget http://download.pingcap.org/tidb-binlog-latest-linux-amd64.tar.gz
 wget http://download.pingcap.org/tidb-binlog-latest-linux-amd64.sha256
 
-# Check the file integrity. If the result is OK, the file is correct. 
+# Check the file integrity. If the result is OK, the file is correct.
 sha256sum -c tidb-binlog-latest-linux-amd64.sha256
 
 # Extract the package.
@@ -64,20 +64,20 @@ cd tidb-binlog-latest-linux-amd64
 - When you deploy a Pump manually, to start the service, follow the order of Pump -> TiDB; to stop the service, follow the order of TiDB -> Pump.
 
     We set the startup parameter `binlog-socket` as the specified unix socket file path of the corresponding parameter `socket` in Pump. The final deployment architecture is as follows:
-    
+
     ![TiDB Pump deployment architecture](../media/tidb_pump_deployment.jpeg)
 
 - Drainer does not support renaming DDL on the table of the ignored schemas (schemas in the filter list).
 
 - To start Drainer in the existing TiDB cluster, usually you need to do a full backup, get the savepoint, import the full backup, and start Drainer and synchronize from the savepoint.
-    
+
     To guarantee the integrity of data, perform the following operations 10 minutes after Pump is started:
 
     - Use the `generate_binlog_position` tool of the [tidb-tools](https://github.com/pingcap/tidb-tools)project to generate the Drainer savepoint file. Use `generate_binlog_position` to compile this tool. See the [README description](https://github.com/pingcap/tidb-tools/blob/master/generate_binlog_position/README.md) for usage. You can also download this tool from [generate_binlog_position](https://download.pingcap.org/generate_binlog_position-latest-linux-amd64.tar.gz) and use `sha256sum` to verify the [sha256](https://download.pingcap.org/generate_binlog_position-latest-linux-amd64.sha256) file.
     - Do a full backup. For example, back up TiDB using mydumper.
     - Import the full backup to the target system.
     - The savepoint file started by the Kafka version of Drainer is stored in the checkpoint table of the downstream database tidb_binlog by default. If no valid data exists in the checkpoint table, configure `initial-commit-ts` to make Drainer work from a specified position when it is started: 
-      
+
         ```
         bin/drainer --config=conf/drainer.toml --data-dir=${drainer_savepoint_dir}
         ```
@@ -95,17 +95,18 @@ cd tidb-binlog-latest-linux-amd64
 
 - Deploy Kafka and ZooKeeper cluster before deploying TiDB-Binlog. Make sure that Kafka is 0.9 version or later.
 
-#### Recommended Kafka cluster configuration  		  
+#### Recommended Kafka cluster configuration
+
 |Name|Number|Memory size|CPU|Hard disk|
 |:---:|:---:|:---:|:---:|:---:|
 |Kafka|3+|16G|8+|2+ 1TB|
 |ZooKeeper|3+|8G|4+|2+ 300G|
-  		  
+
 #### Recommended Kafka parameter configuration
-    
+
 - `auto.create.topics.enable = true`: if no topic exists, Kafka automatically creates a topic on the broker.
 - `broker.id`: a required parameter to identify the Kafka cluster. Keep the parameter value unique. For example, `broker.id = 1`.
-- `fs.file-max = 1000000`: Kafka uses a lot of files and network sockets. It is recommended to change the parameter value to 1000000. Change the value using `vi /etc/sysctl.conf`.   
+- `fs.file-max = 1000000`: Kafka uses a lot of files and network sockets. It is recommended to change the parameter value to 1000000. Change the value using `vi /etc/sysctl.conf`.
 
 ### Deploy Pump using TiDB-Ansible
 
@@ -339,7 +340,7 @@ This example describes how to use Pump/Drainer.
     ```bash
     ./bin/drainer -config drainer.toml
     ```
- 
+
 ## Download PbReader (Linux)
 
 PbReader parses the pb file generated by Drainer and translates it into SQL statements.
@@ -350,21 +351,21 @@ CentOS 7+
 # Download PbReader package
 wget http://download.pingcap.org/pb_reader-latest-linux-amd64.tar.gz
 wget http://download.pingcap.org/pb_reader-latest-linux-amd64.sha256
-    
+
 # Check the file integrity. If the result is OK, the file is correct.
 sha256sum -c pb_reader-latest-linux-amd64.sha256
 
 # Extract the package.
 tar -xzf pb_reader-latest-linux-amd64.tar.gz
 cd pb_reader-latest-linux-amd64
 ```
-    
+
 The PbReader usage example
-    
+
 ```bash
 ./bin/pbReader -binlog-file=binlog-0000000000000000
-```    
-    
+```
+
 ## Monitor TiDB-Binlog
 
 This section introduces how to monitor TiDB-Binlog's status and performance, and display the metrics using Prometheus and Grafana.