From 2efa7bac717c91e986f02990a8c91a7870d57549 Mon Sep 17 00:00:00 2001
From: Vinllen Chen <cvinllen@gmail.com>
Date: Wed, 8 May 2019 19:51:55 +0800
Subject: [PATCH] Feature 1.6 (#57)

* polish

* polish READM again
---
 ChangeLog             | 2 +-
 README.md             | 6 +++---
 conf/redis-shake.conf | 2 +-
 3 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index ea26ce2..0d0e968 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,4 +1,4 @@
-2019-04-21 Alibaba Cloud.
+2019-05-08 Alibaba Cloud.
 	* VERSION: 1.6.0
 	* FEATURE: source address supports cluster.
 	* FEATURE: target address supports several proxies to write data in
diff --git a/README.md b/README.md
index bfe3611..5b924a0 100644
--- a/README.md
+++ b/README.md
@@ -40,9 +40,9 @@ m
 
 # Redis Type
 ---
-Both the source and target type can be single redis, master-slave architecture redis, redis cluster and codis. Although the architecture patterns of different vendors are different for the cluster architecture, we still support different cloud vendors like alibaba-cloud, tencent-cloud and so on.<br>
-If the target is open source redis cluster, redis-shake uses [redis-go-cluster](https://github.com/chasex/redis-go-cluster) driver to write data, otherwise, [redigo](https://github.com/garyburd/redigo) driver is used to insert data in round robin way.<br>
-If the source is redis cluster, redis-shake launches multiple goroutines for parallel pull. User can control the concurrency.<br>
+Both the source and target type can be standalone, opensource cluster and proxy. Although the architecture patterns of different vendors are different for the cluster architecture, we still support different cloud vendors like alibaba-cloud, tencent-cloud and so on.<br>
+If the target is open source redis cluster, redis-shake uses [redis-go-cluster](https://github.com/chasex/redis-go-cluster) driver to write data. When target type is proxy, redis-shakes write data in round-robin way.<br>
+If the source is redis cluster, redis-shake launches multiple goroutines for parallel pull. User can use `rdb.parallel` to control the RDB syncing concurrency.<br>
 The "move slot" operations must be disabled on the source side.<br>
 
 # Code branch rules
diff --git a/conf/redis-shake.conf b/conf/redis-shake.conf
index a57a1d0..d494a04 100644
--- a/conf/redis-shake.conf
+++ b/conf/redis-shake.conf
@@ -70,7 +70,7 @@ rdb.input = local
 # ${output_rdb}.0, ${output_rdb}.1, ${output_rdb}.2
 rdb.output = local_dump
 # the concurrence of fetching data, default is len(source.address) or len(rdb.input).
-# used in `dump`, `sync` and `restore`.
+# used in `dump`, `sync` and `restore`. 0 means default.
 # 拉取的并发度，如果是`dump`或者`sync`，默认是source.address中db的个数，`restore`模式默认len(rdb.input)。
 # 假如db节点/输入的rdb有5个，但rdb.parallel=3，那么一次只会
 # 并发拉取3个db的全量数据，直到某个db的rdb拉取完毕，才会拉取第4个db节点的rdb，以此类推。