You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@servicecomb.apache.org by ni...@apache.org on 2019/08/27 01:01:38 UTC
[servicecomb-docs] 01/04: [SCB-1461] rename
servicecomb.service.registry.client.workerPoolSiz to
servicecomb.service.registry.client.instances.
This is an automated email from the ASF dual-hosted git repository.
ningjiang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/servicecomb-docs.git
commit 80a0afcef8dbbff1b51b3896667b1519812370c8
Author: Liu Huaizhou <li...@163.com>
AuthorDate: Mon Aug 26 20:26:59 2019 +0800
[SCB-1461] rename servicecomb.service.registry.client.workerPoolSiz to servicecomb.service.registry.client.instances.
---
java-chassis-reference/en_US/general-development/visit-sc.md | 4 ++--
java-chassis-reference/zh_CN/general-development/visit-sc.md | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/java-chassis-reference/en_US/general-development/visit-sc.md b/java-chassis-reference/en_US/general-development/visit-sc.md
index 9cc2b77..a07bb91 100755
--- a/java-chassis-reference/en_US/general-development/visit-sc.md
+++ b/java-chassis-reference/en_US/general-development/visit-sc.md
@@ -11,7 +11,7 @@ Developers can configure service center clusters addresses, connection parameter
### Table 1-1 Accessing Common Configuration Items in the Configuration Center
| Configuration Item | Reference / Default | Value Range | Required | Meaning |
-| :--- | :--- | :--- | :--- | :--- | :--- |
+| :--- | :--- | :--- | :--- | :--- |
| servicecomb.service.registry.address | http://127.0.0.1:30100 | | Yes | Service center address information, you can configure multiple, separated by commas. | |
| servicecomb.service.registry.instance. Watch | true | | No | Whether to monitor instance changes in PUSH mode. When it is false, it means using PULL mode. | |
| servicecomb.service.registry. Autodiscovery | false | | No | Whether to automatically discover the address of the service center. This configuration is enabled when a partial address needs to be configured, and other addresses are discovered by the configured service center instance. | |
@@ -22,5 +22,5 @@ Developers can configure service center clusters addresses, connection parameter
| servicecomb.service.registry.client.timeout.request | 30000 | | Request timeout in milliseconds | | |
| servicecomb.service.registry.client.timeout.idle | 60 | | Connection idle timeout in milliseconds | | |
| servicecomb.service.registry.client.timeout.heartbeat | 3000 | | Heartbeat request timeout in milliseconds | | |
-
+| servicecomb.service.registry.client.instances | 1 | | No | the account of verticle instances that Service Registry Client had been deployed | | |
diff --git a/java-chassis-reference/zh_CN/general-development/visit-sc.md b/java-chassis-reference/zh_CN/general-development/visit-sc.md
index de66d18..969d920 100644
--- a/java-chassis-reference/zh_CN/general-development/visit-sc.md
+++ b/java-chassis-reference/zh_CN/general-development/visit-sc.md
@@ -1,4 +1,4 @@
-## 概念阐述
+ ## 概念阐述
系统通过[服务中心](https://github.com/apache/servicecomb-service-center)实现服务之间的发现。服务启动过程中，会向服务中心进行注册。在调用其他服务的时候，会从服务中心查询其他服务的实例信息，比如访问地址、使用的协议以及其他参数。服务中心支持使用PULL和PUSH两种模式通知实例变化。
@@ -22,4 +22,4 @@
| servicecomb.service.registry.client.timeout.request | 30000 | | 请求超时时间 | 单位毫秒 | |
| servicecomb.service.registry.client.timeout.idle | 60 | | 连接闲置超时时间 | 单位秒 | |
| servicecomb.service.registry.client.timeout.heartbeat | 3000 | | 心跳超时时间 | 单位毫秒 | |
-
+| servicecomb.service.registry.client.instances | 1 | | 否 | Service Registry客户端Verticle部署实例的个数 | |