This is an automated email from the ASF dual-hosted git repository.
shaofengshi pushed a commit to branch document
in repository https://gitbox.apache.org/repos/asf/kylin.git
The following commit(s) were added to refs/heads/document by this push:
new f4dd681 update on howto_optimize_build and kylin_cluster
f4dd681 is described below
commit f4dd68115d09eb02bf12f9e74792779eade6e0dc
Author: shaofengshi <shaofeng...@apache.org>
AuthorDate: Fri Sep 14 18:57:45 2018 +0800
update on howto_optimize_build and kylin_cluster
---
website/_docs/howto/howto_optimize_build.cn.md | 2 +-
website/_docs/howto/howto_optimize_build.md | 2 +-
website/_docs/install/kylin_cluster.cn.md | 8 ++++----
website/_docs/install/kylin_cluster.md | 4 ++--
4 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/website/_docs/howto/howto_optimize_build.cn.md
b/website/_docs/howto/howto_optimize_build.cn.md
index 8840a56..85448c6 100644
--- a/website/_docs/howto/howto_optimize_build.cn.md
+++ b/website/_docs/howto/howto_optimize_build.cn.md
@@ -99,7 +99,7 @@ INSERT OVERWRITE TABLE
kylin_intermediate_airline_cube_v3610f668a3cdb437e8373c03
## 构建维度字典
-有了前一步提取的维度列唯一值，Kylin会在内存里构建字典（在下个版本将改为MapReduce任务）。通常这一步比较快，但如果唯一值集合很大，Kylin可能会报出类似“字典不支持过高基数”。对于UHC类型的列，请使用其他编码方式，比如“fixed_length”、“integer”等等。
+有了前一步提取的维度列唯一值，Kylin会在内存里构建字典。通常这一步比较快，但如果唯一值集合很大，Kylin可能会报出类似“字典不支持过高基数”。对于UHC类型的列，请使用其他编码方式，比如“fixed_length”、“integer”等等。
## 保存cuboid的统计数据和创建 HTable
diff --git a/website/_docs/howto/howto_optimize_build.md
b/website/_docs/howto/howto_optimize_build.md
index 75b64f4..0f68740 100644
--- a/website/_docs/howto/howto_optimize_build.md
+++ b/website/_docs/howto/howto_optimize_build.md
@@ -111,7 +111,7 @@ You can reduce the sampling percentage
(kylin.job.cubing.inmem.sampling.percen i
## Build Dimension Dictionary
-With the distinct values fetched in previous step, Kylin will build
dictionaries in memory (in next version this will be moved to MR). Usually this
step is fast, but if the value set is large, Kylin may report error like "Too
high cardinality is not suitable for dictionary". For UHC column, please use
other encoding method for the UHC column, such as "fixed_length", "integer" and
so on.
+With the distinct values fetched in previous step, Kylin will build
dictionaries in memory. Usually this step is fast, but if the value set is
large, Kylin may report error like "Too high cardinality is not suitable for
dictionary". For UHC column, please use other encoding method for the UHC
column, such as "fixed_length", "integer" and so on.
diff --git a/website/_docs/install/kylin_cluster.cn.md
b/website/_docs/install/kylin_cluster.cn.md
index a612cd1..881537a 100644
--- a/website/_docs/install/kylin_cluster.cn.md
+++ b/website/_docs/install/kylin_cluster.cn.md
@@ -16,7 +16,7 @@ Kylin 实例是无状态的。其运行时状态存于存储在 HBase (由 `conf
* **query** : 只运行 query engine; Kylin query engine 接收和回应你的 SQL 查询;
* **all** : 在实例中既运行 job engine 也运行 query engines。
-注意只有一个实例可以运行 job engine ("all" 或 "job" 模式), 其他必须是 "query" 模式。
+注意默认情况下只有一个实例可以运行 job engine ("all" 或 "job" 模式), 其它需要是 "query" 模式。
下图中描绘了一个典型场景:
@@ -24,10 +24,10 @@ Kylin 实例是无状态的。其运行时状态存于存储在 HBase (由 `conf
### 配置多个 Kylin 服务器
-当您在拥有多个 Kylin 服务器实例的集群运行 Kylin 时, 请确保您为每一个实例在 `conf/kylin.properties`
中正确的配置了以下属性。
+当您在拥有多个 Kylin 服务器实例的集群运行 Kylin 时, 请确保您为每个实例在 `conf/kylin.properties`
中正确的配置了以下属性。
* `kylin.rest.servers`
- 使用中的服务器列表, 当事件变化时，让一个实例去通知其他服务器。例如:
+ Kylin 节点列表,
要包括每个节点（强调一下，是每个，包括自己！）当事件变化时，接收变化的节点需要通知其它节点（也包括自己）清理缓存。例如:
```
kylin.rest.servers=host1:7070,host2:7070
@@ -42,7 +42,7 @@ kylin.rest.servers=host1:7070,host2:7070
kylin.server.mode=all
```
-也即默认情况下，只有一个节点用于调度构建任务的执行。如果您需要配置多个节点同时执行任务构建，以满足高可用和高并发的需求，请参考 "启用多个任务引擎"
的内容，在 [高级设置](advance_settings.html) 页.
+默认情况下，只有一个节点用于调度构建任务的执行。如果您需要配置多个节点同时执行任务构建，以满足高可用和高并发的需求，请参考 "启用多个任务引擎" 的内容，在
[高级设置](advance_settings.html) 页.
### 安装负载均衡器
diff --git a/website/_docs/install/kylin_cluster.md
b/website/_docs/install/kylin_cluster.md
index 6a3545e..65ee0fe 100644
--- a/website/_docs/install/kylin_cluster.md
+++ b/website/_docs/install/kylin_cluster.md
@@ -26,7 +26,7 @@ A typical scenario is depicted in the following chart:
### Configure Multiple Kylin Servers
-If you are running Kylin in a cluster where you have multiple Kylin server
instances, please make sure you have the following property correctly
configured in `conf/kylin.properties` for EVERY instance.
+If you are running Kylin in a cluster where you have multiple Kylin server
instances, please make sure you have the following property correctly
configured in `conf/kylin.properties` for EVERY instance (both job and query).
* `kylin.rest.servers`
List of servers in use, this enables one instance to notify other
servers when there is event change. For example:
@@ -36,7 +36,7 @@ kylin.rest.servers=host1:7070,host2:7070
```
* `kylin.server.mode`
- Make sure there is only one instance whose `kylin.server.mode` is set
to "all" or "job", others should be "query"
+ By default, only one instance whose `kylin.server.mode` is set to "all"
or "job", the others be "query"
```
kylin.server.mode=all
