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/06 01:30:35 UTC
[servicecomb-website] branch asf-site updated: Publish the website
This is an automated email from the ASF dual-hosted git repository.
ningjiang pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/servicecomb-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new e612542 Publish the website
e612542 is described below
commit e612542c9912aec6000a80ed567b8f6216250f72
Author: Willem Jiang <wi...@gmail.com>
AuthorDate: Tue Aug 6 09:30:19 2019 +0800
Publish the website
---
.../index.html | 18 +-
.../distributed-tracing/index.html | 16 +-
.../quick-start-advance/flow-control/index.html | 8 +-
.../quick-start-advance/load-balance/index.html | 8 +-
.../service-management/index.html | 8 +-
content/cn/users/service-configurations/index.html | 192 ++-------------------
.../distributed-tracing/index.html | 17 +-
.../quick-start-advance/flow-control/index.html | 8 +-
.../quick-start-advance/load-balance/index.html | 8 +-
.../service-management/index.html | 8 +-
content/feed.xml | 2 +-
content/users/service-configurations/index.html | 191 ++------------------
12 files changed, 112 insertions(+), 372 deletions(-)
diff --git a/content/cn/docs/distributed-transactions-saga-implementation/index.html b/content/cn/docs/distributed-transactions-saga-implementation/index.html
index 82141e3..a3e7b37 100644
--- a/content/cn/docs/distributed-transactions-saga-implementation/index.html
+++ b/content/cn/docs/distributed-transactions-saga-implementation/index.html
@@ -381,13 +381,18 @@
<section class="page__content" itemprop="text">
<h2 id="saga分布式事务解决方案与实践">Saga分布式事务解决方案与实践</h2>
+<p>本文为2018年QConBeijing Saga分布式事务解决方案与实践演讲实录。 <br />
+【2019年8月更新】目前我们的集中式的Saga解决方案ServiceComb已经发布了7版，去年底项目更名为 ServiceComb Pack，提供TCC的支持。大家可以访问我们项目的<a href="https://github.com/apache/servicecomb-pack">github地址</a>，获取到更多与项目相关的详细信息，欢迎大家为项目加星哦。</p>
+
<p><img src="/assets/images/saga/Saga.001.jpeg" alt="" /></p>
<p><img src="/assets/images/saga/Saga.002.jpeg" alt="" />
-我先介绍一下我自己，我叫姜宁，来自于华为开源研究中心，现在负责的是ServiceComb这个开源项目。ServiceComb这个项目已经进到Apache孵化，应该是去年11月份时进到Apache孵化的，这个月我们帮刚发了1.0M1版，但对于SAGA来说我们属于探索的阶段，发布了0.1.0。</p>
+我先介绍一下我自己，我叫姜宁，来自于华为开源能力中心，现在负责的是ServiceComb这个开源项目。ServiceComb这个项目已经进到Apache孵化，应该是去年11月份时进到Apache孵化的，这个月我们帮刚发了1.0M1版，但对于SAGA来说我们属于探索的阶段，发布了0.1.0。</p>
<p>我参与过Apache一些项目，我也是Apache的 Member，是Apache CXF, Apache Camel 还有的PMC。还有一件事情，前一段时间帮阿里同学孵化 RocketMQ，我是以导师的身份参与的，属于见习的Mentor.这回带着ServiceComb这个项目，我感觉我把很多角色都玩了一遍。后面如果大家对开源项目进入Apache孵化感兴趣的话也可以来找到。</p>
+<p>【2019年8月更新】最近发现Apache Camel的国内小伙伴越来越多， 有兴趣想加入的朋友可以给我发邮件 willem.jiang AT gmail.</p>
+
<p><img src="/assets/images/saga/Saga.003.jpeg" alt="" /></p>
<p>今天的议题围绕几个方面来展开，一个是微服务事务一致性的问题，然后讲一讲业界的SAGA解决方案，我们在ServiceComb里也提供了SAGA的实现。另外一件事情，我项目这边也在招新，欢迎广大感兴趣的同学一会儿加我微信。我们现在项目其实架子也都搭得不错了，基本功能都实现了，就是等着大家跳到碗里面，一起来解决微服务事务一致性问题。</p>
@@ -557,9 +562,16 @@
<p>还有Omega需要解决多线程共享调用的问题。</p>
-<p>我们问题都列在下面的JIRA上面，大家可以通过这个<a href="https://issues.apache.org/jira/browse/SCB-333?jql=project%20%3D%20SCB%20AND%20status%20%3D%20Open%20AND%20fixVersion%20in%20(EMPTY%2C%20java-chassis-1.0.0-m2)%20AND%20labels%20%3D%20newbie">链接</a>入门任务。</p>
+<p>【2019年8月更新】TCC的功能我们已经在<a href="https://github.com/apache/servicecomb-pack/releases/tag/0.3.0">Pack 0.3.0</a>中提供, 并且在 <a href="https://github.com/apache/servicecomb-pack/releases/tag/0.4.0">Pack 0.4.0</a>中提供了Alpha多活支持。现在开发的ServiceComb Pack 0.5.0 做了两个比较大的改进， 一个是在客户端（Omega）提供异步调用的支持， 一个是服务端（Alpha）采用状态机追踪服务的调用情况。</p>
+
+<p>大家可以通过查看我们的<a href="https://github.com/apache/servicecomb-pack/blob/master/ROADMAP.md">线路图</a>, 或者通过<a href="https://gitter.im/ServiceCombUsers/Saga">gitter</a>与社区开发人员互动。</p>
-<p><img src="/assets/images/saga/Saga.037.jpeg" alt="" /></p>
+<p>有关ServiceComb Pack交互的细节以及相关的架构设计，大家可以参考下面两篇文章:</p>
+<ul>
+ <li><a href="http://servicecomb.apache.org/cn/docs/distributed-transaction-of-services-1/">基于服务的分布式事务(上篇)</a></li>
+ <li><a href="http://servicecomb.apache.org/cn/docs/distributed-transaction-of-services-2/">基于服务的分布式事务(下篇)</a>
+<img src="/assets/images/saga/Saga.037.jpeg" alt="" /></li>
+</ul>
<p>简单小节一下，我们对事务一致性做了简单的回顾，业界的SAGA解决方案也提了一下，简单介绍一下ServiceComb的Saga实现，以及我们后续的开发计划。</p>
diff --git a/content/cn/docs/quick-start-advance/distributed-tracing/index.html b/content/cn/docs/quick-start-advance/distributed-tracing/index.html
index 2bac60c..2b37936 100644
--- a/content/cn/docs/quick-start-advance/distributed-tracing/index.html
+++ b/content/cn/docs/quick-start-advance/distributed-tracing/index.html
@@ -420,14 +420,26 @@
<li>
<p>重启 <em>体质指数计算器</em> 微服务：</p>
- <div class="language-bash highlighter-rouge"><pre class="highlight"><code>mvn spring-boot:run -Drun.jvmArguments<span class="o">=</span><span class="s2">"-Dcse.handler.chain.Provider.default=tracing-provider"</span>
+ <div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="c">#spring-boot-maven-plugin 1.x</span>
+mvn spring-boot:run -Drun.jvmArguments<span class="o">=</span><span class="s2">"-Dcse.handler.chain.Provider.default=tracing-provider"</span>
+</code></pre>
+ </div>
+ <p>or</p>
+ <div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="c">#spring-boot-maven-plugin 2.x</span>
+ mvn spring-boot:run -Dspring-boot.run.jvmArguments<span class="o">=</span><span class="s2">"-Dcse.handler.chain.Provider.default=tracing-provider"</span>
</code></pre>
</div>
</li>
<li>
<p>重启 <em>体质指数界面</em> 微服务：</p>
- <div class="language-bash highlighter-rouge"><pre class="highlight"><code>mvn spring-boot:run -Drun.jvmArguments<span class="o">=</span><span class="s2">"-Dservicecomb.tracing.enabled=true"</span>
+ <div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="c">#spring-boot-maven-plugin 1.x</span>
+mvn spring-boot:run -Drun.jvmArguments<span class="o">=</span><span class="s2">"-Dservicecomb.tracing.enabled=true"</span>
+</code></pre>
+ </div>
+ <p>or</p>
+ <div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="c">#spring-boot-maven-plugin 2.x</span>
+mvn spring-boot:run -Dspring-boot.run.jvmArguments<span class="o">=</span><span class="s2">"-Dservicecomb.tracing.enabled=true"</span>
</code></pre>
</div>
</li>
diff --git a/content/cn/docs/quick-start-advance/flow-control/index.html b/content/cn/docs/quick-start-advance/flow-control/index.html
index d6c2793..8c98ef6 100644
--- a/content/cn/docs/quick-start-advance/flow-control/index.html
+++ b/content/cn/docs/quick-start-advance/flow-control/index.html
@@ -404,7 +404,13 @@
<p>体质指数应用中已配置好了上述配置项，您只需关闭之前运行的 <strong>体质指数计算器</strong>，然后再用以下指令重新运行即可：</p>
-<div class="language-bash highlighter-rouge"><pre class="highlight"><code>mvn spring-boot:run -Drun.jvmArguments<span class="o">=</span><span class="s2">"-Dcse.handler.chain.Provider.default=qps-flowcontrol-provider -Dcse.flowcontrol.Provider.qps.limit.gateway=1"</span>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="c">#spring-boot-maven-plugin 1.x</span>
+mvn spring-boot:run -Drun.jvmArguments<span class="o">=</span><span class="s2">"-Dcse.handler.chain.Provider.default=qps-flowcontrol-provider -Dcse.flowcontrol.Provider.qps.limit.gateway=1"</span>
+</code></pre>
+</div>
+<p>or</p>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="c">#spring-boot-maven-plugin 2.x</span>
+mvn spring-boot:run -Dspring-boot.run.jvmArguments<span class="o">=</span><span class="s2">"-Dcse.handler.chain.Provider.default=qps-flowcontrol-provider -Dcse.flowcontrol.Provider.qps.limit.gateway=1"</span>
</code></pre>
</div>
diff --git a/content/cn/docs/quick-start-advance/load-balance/index.html b/content/cn/docs/quick-start-advance/load-balance/index.html
index bd90735..0e729ea 100644
--- a/content/cn/docs/quick-start-advance/load-balance/index.html
+++ b/content/cn/docs/quick-start-advance/load-balance/index.html
@@ -379,7 +379,13 @@
<p>对 <em>体质指数计算器</em> 微服务进行水平扩展，使其运行实例数为2，即新增一个运行实例：</p>
-<div class="language-bash highlighter-rouge"><pre class="highlight"><code>mvn spring-boot:run -Drun.jvmArguments<span class="o">=</span><span class="s2">"-Dcse.rest.address=0.0.0.0:7778"</span>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="c">#spring-boot-maven-plugin 1.x</span>
+mvn spring-boot:run -Drun.jvmArguments<span class="o">=</span><span class="s2">"-Dcse.rest.address=0.0.0.0:7778"</span>
+</code></pre>
+</div>
+<p>or</p>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="c">#spring-boot-maven-plugin 2.x</span>
+mvn spring-boot:run -Dspring-boot.run.jvmArguments<span class="o">=</span><span class="s2">"-Dcse.rest.address=0.0.0.0:7778"</span>
</code></pre>
</div>
diff --git a/content/cn/docs/quick-start-advance/service-management/index.html b/content/cn/docs/quick-start-advance/service-management/index.html
index 02e8d44..d73f117 100644
--- a/content/cn/docs/quick-start-advance/service-management/index.html
+++ b/content/cn/docs/quick-start-advance/service-management/index.html
@@ -406,7 +406,13 @@
<p>体质指数应用中已配置好了上述配置项，您只需重新运行 <strong>体质指数计算器</strong>：</p>
-<div class="language-bash highlighter-rouge"><pre class="highlight"><code>mvn spring-boot:run -Drun.jvmArguments<span class="o">=</span><span class="s2">"-Dcse.handler.chain.Provider.default=bizkeeper-provider -Dcse.circuitBreaker.Provider.calculator.requestVolumeThreshold=3 -Dcse.fallbackpolicy.Provider.policy=returnnull"</span>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="c">#spring-boot-maven-plugin 1.x</span>
+mvn spring-boot:run -Drun.jvmArguments<span class="o">=</span><span class="s2">"-Dcse.handler.chain.Provider.default=bizkeeper-provider -Dcse.circuitBreaker.Provider.calculator.requestVolumeThreshold=3 -Dcse.fallbackpolicy.Provider.policy=returnnull"</span>
+</code></pre>
+</div>
+<p>or</p>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="c">#spring-boot-maven-plugin 2.x</span>
+mvn spring-boot:run -Dspring-boot.run.jvmArguments<span class="o">=</span><span class="s2">"-Dcse.handler.chain.Provider.default=bizkeeper-provider -Dcse.circuitBreaker.Provider.calculator.requestVolumeThreshold=3 -Dcse.fallbackpolicy.Provider.policy=returnnull"</span>
</code></pre>
</div>
diff --git a/content/cn/users/service-configurations/index.html b/content/cn/users/service-configurations/index.html
index ac5102a..8feaa6c 100644
--- a/content/cn/users/service-configurations/index.html
+++ b/content/cn/users/service-configurations/index.html
@@ -347,198 +347,30 @@
<nav class="toc">
<!-- <header><h4 class="nav__title"><i class="fa fa-file-text"></i> 在本页上</h4></header> -->
<ul class="toc__menu" id="markdown-toc">
- <li><a href="#负载均衡策略" id="markdown-toc-负载均衡策略">负载均衡策略</a> <ul>
- <li><a href="#场景描述" id="markdown-toc-场景描述">场景描述</a></li>
- <li><a href="#配置说明" id="markdown-toc-配置说明">配置说明</a></li>
- <li><a href="#示例代码" id="markdown-toc-示例代码">示例代码</a></li>
- </ul>
- </li>
- <li><a href="#自定义路由策略" id="markdown-toc-自定义路由策略">自定义路由策略</a></li>
+ <li><a href="#负载均衡策略" id="markdown-toc-负载均衡策略">负载均衡策略</a></li>
<li><a href="#限流策略" id="markdown-toc-限流策略">限流策略</a> <ul>
- <li><a href="#场景描述-1" id="markdown-toc-场景描述-1">场景描述</a></li>
+ <li><a href="#场景描述" id="markdown-toc-场景描述">场景描述</a></li>
<li><a href="#注意事项" id="markdown-toc-注意事项">注意事项</a></li>
- <li><a href="#配置说明-1" id="markdown-toc-配置说明-1">配置说明</a></li>
+ <li><a href="#配置说明" id="markdown-toc-配置说明">配置说明</a></li>
</ul>
</li>
<li><a href="#降级策略" id="markdown-toc-降级策略">降级策略</a> <ul>
<li><a href="#概念阐述" id="markdown-toc-概念阐述">概念阐述</a></li>
- <li><a href="#场景描述-2" id="markdown-toc-场景描述-2">场景描述</a></li>
- <li><a href="#配置说明-2" id="markdown-toc-配置说明-2">配置说明</a></li>
+ <li><a href="#场景描述-1" id="markdown-toc-场景描述-1">场景描述</a></li>
+ <li><a href="#配置说明-1" id="markdown-toc-配置说明-1">配置说明</a></li>
</ul>
</li>
- <li><a href="#示例代码-1" id="markdown-toc-示例代码-1">示例代码</a></li>
+ <li><a href="#示例代码" id="markdown-toc-示例代码">示例代码</a></li>
</ul>
</nav>
</aside>
<h2 id="负载均衡策略">负载均衡策略</h2>
-<h3 id="场景描述">场景描述</h3>
-
-<p> ServiceComb提供了基于Ribbon的负载均衡方案，用户可以通过配置文件配置负载均衡策略，当前支持随机、顺序、基于响应时间的权值等多种负载均衡路由策略。</p>
-
-<h3 id="配置说明">配置说明</h3>
-
-<p> 负载均衡策略在microservice.yaml文件中配置，配置项为<code class="highlighter-rouge">servicecomb.loadbalance.[MicroServiceName].[property name]</code>，其中若省略MicroServiceName，则为全局配置；若指定MicroServiceName，则为针对特定微服务的配置。</p>
-
-<p> <strong>表1 配置项说明</strong></p>
-
-<table>
- <thead>
- <tr>
- <th style="text-align: left">配置项</th>
- <th style="text-align: left">默认值</th>
- <th style="text-align: left">取值范围</th>
- <th style="text-align: left">是否必选</th>
- <th style="text-align: left">含义</th>
- <th style="text-align: left">注意</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td style="text-align: left">servicecomb.loadbalance.NFLoadBalancerRuleClassName</td>
- <td style="text-align: left">com.netflix.loadbalancer.RoundRobinRule</td>
- <td style="text-align: left">com.netflix.loadbalancer.RoundRobinRule（轮询）com.netflix.loadbalancer.RandomRule（随机）com.netflix.loadbalancer.WeightedResponseTimeRule（服务器响应时间权值）org.apache.servicecomb.loadbalance.SessionStickinessRule（会话保持）</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">负载均衡路由策略</td>
- <td style="text-align: left">-</td>
- </tr>
- <tr>
- <td style="text-align: left">servicecomb.loadbalance.SessionStickinessRule.sessionTimeoutInSeconds</td>
- <td style="text-align: left">30</td>
- <td style="text-align: left">Integer</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">客户端闲置时间，超过限制后选择后面的服务器。</td>
- <td style="text-align: left">暂不支持微服务配置。e.g. servicecomb.loadbalance.SessionStickinessRule.sessionTimeoutInSeconds，不能配置为servicecomb.loadbalance.DemoService.SessionStickinessRule.sessionTimeoutInSeconds</td>
- </tr>
- <tr>
- <td style="text-align: left">servicecomb.loadbalance.SessionStickinessRule.successiveFailedTimes</td>
- <td style="text-align: left">5</td>
- <td style="text-align: left">Integer</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">客户端失败次数，超过后会切换服务器</td>
- <td style="text-align: left">暂不支持微服务配置</td>
- </tr>
- <tr>
- <td style="text-align: left">servicecomb.loadbalance.retryEnabled</td>
- <td style="text-align: left">FALSE</td>
- <td style="text-align: left">Boolean</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">负载均衡捕获到服务调用异常，是否进行重试</td>
- <td style="text-align: left">-</td>
- </tr>
- <tr>
- <td style="text-align: left">servicecomb.loadbalance.retryOnNext</td>
- <td style="text-align: left">0</td>
- <td style="text-align: left">Integer</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">尝试新的服务器的次数</td>
- <td style="text-align: left">-</td>
- </tr>
- <tr>
- <td style="text-align: left">servicecomb.loadbalance.retryOnSame</td>
- <td style="text-align: left">0</td>
- <td style="text-align: left">Integer</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">同一个服务器尝试的次数</td>
- <td style="text-align: left">-</td>
- </tr>
- <tr>
- <td style="text-align: left">servicecomb.loadbalance.isolation.enabled</td>
- <td style="text-align: left">FALSE</td>
- <td style="text-align: left">Boolean</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">是否开启故障实例隔离功能</td>
- <td style="text-align: left">-</td>
- </tr>
- <tr>
- <td style="text-align: left">servicecomb.loadbalance.isolation.enableRequestThreshold</td>
- <td style="text-align: left">20</td>
- <td style="text-align: left">Integer</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">当实例的调用总次数达到该值时开始进入隔离逻辑门槛</td>
- <td style="text-align: left">-</td>
- </tr>
- <tr>
- <td style="text-align: left">servicecomb.loadbalance.isolation.errorThresholdPercentage</td>
- <td style="text-align: left">20</td>
- <td style="text-align: left">Integer，区间为(0,100]</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">实例故障隔离错误百分比</td>
- <td style="text-align: left">-</td>
- </tr>
- <tr>
- <td style="text-align: left">servicecomb.loadbalance.isolation.singleTestTime</td>
- <td style="text-align: left">10000</td>
- <td style="text-align: left">Integer</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">故障实例单点测试时间</td>
- <td style="text-align: left">单位为ms</td>
- </tr>
- <tr>
- <td style="text-align: left">servicecomb.loadbalance.transactionControl.policy</td>
- <td style="text-align: left">org.apache.servicecomb.loadbalance.filter.SimpleTransactionControlFilter</td>
- <td style="text-align: left">-</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">动态路由分流策略</td>
- <td style="text-align: left">框架提供了简单的分流机制，开发者也可以实现自定义的分流过滤策略</td>
- </tr>
- <tr>
- <td style="text-align: left">servicecomb.loadbalance.transactionControl.options</td>
- <td style="text-align: left">-</td>
- <td style="text-align: left">key/value pairs</td>
- <td style="text-align: left">否</td>
- <td style="text-align: left">针对SimpleTransactionControlFilter分流策略的配置项，可添加任意项过滤标签</td>
- <td style="text-align: left">-</td>
- </tr>
- </tbody>
-</table>
-
-<h3 id="示例代码">示例代码</h3>
-
-<p> 负载均衡策略配置在src/main/resources/microservice.yaml文件中。</p>
-
-<p> 配置处理链：</p>
-
-<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">servicecomb</span><span class="pi">:</span>
- <span class="c1"># other configurations omitted</span>
- <span class="s">handler</span><span class="pi">:</span>
- <span class="s">chain</span><span class="pi">:</span>
- <span class="s">Consumer</span><span class="pi">:</span>
- <span class="s">default</span><span class="pi">:</span> <span class="s">loadbalance</span>
- <span class="c1"># other configurations omitted</span>
-</code></pre>
-</div>
-
-<p> 增加路由策略：</p>
-
-<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">servicecomb：</span>
- <span class="s"># other configurations omitted</span>
- <span class="s">loadbalance</span><span class="pi">:</span>
- <span class="s">NFLoadBalancerRuleClassName</span><span class="pi">:</span> <span class="s">com.netflix.loadbalancer.RoundRobinRule</span>
- <span class="c1"># other configurations omitted</span>
-</code></pre>
-</div>
-
-<h2 id="自定义路由策略">自定义路由策略</h2>
-
-<p> 用户可以在ServiceComb提供的路由策略框架下根据业务需要，通过编程的方式来开发路由策略。实施步骤如下：</p>
-
-<ul>
- <li>
- <p>实现接口<code class="highlighter-rouge">com.netflix.loadbalancer.IRule</code>中定义的接口方法。
-路由选择逻辑在public Server choose(Object key)方法中实现。LoadBalancerStats是一个封装了负载均衡器当前运行状态的一个结构。通过获取stats中各个实例的运行指标，在choose方法中，判定将当前请求路由到哪个实例上进行处理。处理风格可以参照<code class="highlighter-rouge">org.apache.servicecomb.loadbalance.SessionStickinessRule</code>。</p>
- </li>
- <li>
- <p>编译开发的策略，保证生成的class在classpath下。</p>
- </li>
- <li>
- <p>通过SDK配置该路由策略，假如是<code class="highlighter-rouge">AbcRule</code>。则配置如下： <code class="highlighter-rouge">servicecomb.loadbalance.NFLoadBalancerRuleClassName=org.apache.servicecomb.ribbon.rule.AbcRule</code></p>
- </li>
-</ul>
+<p>本章节的内容已过时，新的负载均衡策略说明见<a href="https://docs.servicecomb.io/java-chassis/zh_CN/references-handlers/loadbalance.html">负载均衡</a></p>
<h2 id="限流策略">限流策略</h2>
-<h3 id="场景描述-1">场景描述</h3>
+<h3 id="场景描述">场景描述</h3>
<p>用户在provider端使用限流策略，可以限制指定微服务向其发送请求的频率，达到限制每秒钟最大请求数量的效果。</p>
@@ -550,7 +382,7 @@
<li>流量控制是微服务级的，不是进程级的。</li>
</ol>
-<h3 id="配置说明-1">配置说明</h3>
+<h3 id="配置说明">配置说明</h3>
<p> 限流策略配置在microservice.yaml文件中，相关配置项见表2。要开启服务提供者端的限流策略，还需要在处理链中配置服务端限流handler，并添加pom依赖。</p>
@@ -629,11 +461,11 @@
<p>把这些概念联系起来：当”隔离”措施检测到N次请求中共有M次错误的时候，”熔断”不再发送后续请求，调用”容错”处理函数。这个技术上的定义，是和Netflix Hystrix一致的，通过这个定义，非常容易理解它提供的配置项，参考：<a href="https://github.com/Netflix/Hystrix/wiki/Configuration">https://github.com/Netflix/Hystrix/wiki/Configuration</a>。当前ServiceComb提供两种容错方式，分别为返回null值和抛出异常。</p>
-<h3 id="场景描述-2">场景描述</h3>
+<h3 id="场景描述-1">场景描述</h3>
<p>用户通过配置降级策略，可以设置微服务的异常处理策略。</p>
-<h3 id="配置说明-2">配置说明</h3>
+<h3 id="配置说明-1">配置说明</h3>
<p> 配置项如表所示。</p>
@@ -752,7 +584,7 @@
<p class="notice--warning"><strong>注意：</strong> 谨慎使用servicecomb.isolation.timeout.enabled=true。因为系统处理链都是异步执行，中间处理链的返回，会导致后面处理链的逻辑处理效果丢失。尽可能将servicecomb.isolation.timeout.enabled保持默认值false，并且正确设置网络层超时时间servicecomb.request.timeout=30000。</p>
-<h2 id="示例代码-1">示例代码</h2>
+<h2 id="示例代码">示例代码</h2>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">servicecomb</span><span class="pi">:</span>
<span class="s">handler</span><span class="pi">:</span>
diff --git a/content/docs/quick-start-advance/distributed-tracing/index.html b/content/docs/quick-start-advance/distributed-tracing/index.html
index 290e525..01c6b98 100644
--- a/content/docs/quick-start-advance/distributed-tracing/index.html
+++ b/content/docs/quick-start-advance/distributed-tracing/index.html
@@ -422,11 +422,22 @@
<div class="language-bash highlighter-rouge"><pre class="highlight"><code>mvn spring-boot:run -Drun.jvmArguments<span class="o">=</span><span class="s2">"-Dcse.handler.chain.Provider.default=tracing-provider"</span>
</code></pre>
</div>
+ <p>or</p>
+ <div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="c">#spring-boot-maven-plugin 2.x</span>
+ mvn spring-boot:run -Dspring-boot.run.jvmArguments<span class="o">=</span><span class="s2">"-Dcse.handler.chain.Provider.default=tracing-provider"</span>
+</code></pre>
+ </div>
</li>
<li>
<p>Restart <em>BMI web service</em> with the following command:</p>
- <div class="language-bash highlighter-rouge"><pre class="highlight"><code>mvn spring-boot:run -Drun.jvmArguments<span class="o">=</span><span class="s2">"-Dservicecomb.tracing.enabled=true"</span>
+ <div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="c">#spring-boot-maven-plugin 1.x</span>
+mvn spring-boot:run -Drun.jvmArguments<span class="o">=</span><span class="s2">"-Dservicecomb.tracing.enabled=true"</span>
+</code></pre>
+ </div>
+ <p>or</p>
+ <div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="c">#spring-boot-maven-plugin 2.x</span>
+ mvn spring-boot:run -Dspring-boot.run.jvmArguments<span class="o">=</span><span class="s2">"--Dservicecomb.tracing.enabled=true"</span>
</code></pre>
</div>
</li>
@@ -462,6 +473,10 @@
</li>
</ul>
+<div class="highlighter-rouge"><pre class="highlight"><code>
+</code></pre>
+</div>
+
</section>
diff --git a/content/docs/quick-start-advance/flow-control/index.html b/content/docs/quick-start-advance/flow-control/index.html
index 56b8471..fa8d8bb 100644
--- a/content/docs/quick-start-advance/flow-control/index.html
+++ b/content/docs/quick-start-advance/flow-control/index.html
@@ -403,7 +403,13 @@
<p>The above configurations have already set up in the code. All you need to do is to stop all <strong>BMI calculator services</strong> and then start a new one with the following command:</p>
-<div class="language-bash highlighter-rouge"><pre class="highlight"><code>mvn spring-boot:run -Drun.jvmArguments<span class="o">=</span><span class="s2">"-Dcse.handler.chain.Provider.default=qps-flowcontrol-provider -Dcse.flowcontrol.Provider.qps.limit.gateway=1"</span>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="c">#spring-boot-maven-plugin 1.x</span>
+mvn spring-boot:run -Drun.jvmArguments<span class="o">=</span><span class="s2">"-Dcse.handler.chain.Provider.default=qps-flowcontrol-provider -Dcse.flowcontrol.Provider.qps.limit.gateway=1"</span>
+</code></pre>
+</div>
+<p>or</p>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="c">#spring-boot-maven-plugin 2.x</span>
+mvn spring-boot:run -Dspring-boot.run.jvmArguments<span class="o">=</span><span class="s2">"-Dcse.handler.chain.Provider.default=qps-flowcontrol-provider -Dcse.flowcontrol.Provider.qps.limit.gateway=1"</span>
</code></pre>
</div>
diff --git a/content/docs/quick-start-advance/load-balance/index.html b/content/docs/quick-start-advance/load-balance/index.html
index 24ab55f..e77ea9d 100644
--- a/content/docs/quick-start-advance/load-balance/index.html
+++ b/content/docs/quick-start-advance/load-balance/index.html
@@ -377,7 +377,13 @@
<h2 id="verification">Verification</h2>
<p>Run one more <em>BMI calculator service</em> with the following command:</p>
-<div class="language-bash highlighter-rouge"><pre class="highlight"><code>mvn spring-boot:run -Drun.jvmArguments<span class="o">=</span><span class="s2">"-Dcse.rest.address=0.0.0.0:7778"</span>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="c">#spring-boot-maven-plugin 1.x</span>
+mvn spring-boot:run -Drun.jvmArguments<span class="o">=</span><span class="s2">"-Dcse.rest.address=0.0.0.0:7778"</span>
+</code></pre>
+</div>
+<p>or</p>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="c">#spring-boot-maven-plugin 2.x</span>
+mvn spring-boot:run -Dspring-boot.run.jvmArguments<span class="o">=</span><span class="s2">"-Dcse.rest.address=0.0.0.0:7778"</span>
</code></pre>
</div>
diff --git a/content/docs/quick-start-advance/service-management/index.html b/content/docs/quick-start-advance/service-management/index.html
index 5022e28..1a5b601 100644
--- a/content/docs/quick-start-advance/service-management/index.html
+++ b/content/docs/quick-start-advance/service-management/index.html
@@ -405,7 +405,13 @@
<p>The above configurations have already set up in the code. All you need to do is to restart the <em>BMI calculator services</em> with the following command:</p>
-<div class="language-bash highlighter-rouge"><pre class="highlight"><code>mvn spring-boot:run -Drun.jvmArguments<span class="o">=</span><span class="s2">"-Dcse.handler.chain.Provider.default=bizkeeper-provider -Dcse.circuitBreaker.Provider.calculator.requestVolumeThreshold=3 -Dcse.fallbackpolicy.Provider.policy=returnnull"</span>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="c">#spring-boot-maven-plugin 1.x</span>
+mvn spring-boot:run -Drun.jvmArguments<span class="o">=</span><span class="s2">"-Dcse.handler.chain.Provider.default=bizkeeper-provider -Dcse.circuitBreaker.Provider.calculator.requestVolumeThreshold=3 -Dcse.fallbackpolicy.Provider.policy=returnnull"</span>
+</code></pre>
+</div>
+<p>or</p>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="c">#spring-boot-maven-plugin 2.x</span>
+mvn spring-boot:run -Dspring-boot.run.jvmArguments<span class="o">=</span><span class="s2">"-Dcse.handler.chain.Provider.default=bizkeeper-provider -Dcse.circuitBreaker.Provider.calculator.requestVolumeThreshold=3 -Dcse.fallbackpolicy.Provider.policy=returnnull"</span>
</code></pre>
</div>
diff --git a/content/feed.xml b/content/feed.xml
index 1537498..9237999 100644
--- a/content/feed.xml
+++ b/content/feed.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.4.3">Jekyll</generator><link href="/feed.xml" rel="self" type="application/atom+xml" /><link href="/" rel="alternate" type="text/html" /><updated>2019-07-11T17:45:19+08:00</updated><id>/</id><title type="html">Apache ServiceComb</title><subtitle>The homepage of ServiceComb</subtitle><author><name>{"name"=>nil, "avatar"=>"/assets [...]
+<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.4.3">Jekyll</generator><link href="/feed.xml" rel="self" type="application/atom+xml" /><link href="/" rel="alternate" type="text/html" /><updated>2019-08-06T09:15:57+08:00</updated><id>/</id><title type="html">Apache ServiceComb</title><subtitle>The homepage of ServiceComb</subtitle><author><name>{"name"=>nil, "avatar"=>"/assets [...]
<p>基于微服务架构的应用相对于单体架构的应用而言在验收测试阶段具有以下挑战：</p>
diff --git a/content/users/service-configurations/index.html b/content/users/service-configurations/index.html
index 0692d14..6c95bdd 100644
--- a/content/users/service-configurations/index.html
+++ b/content/users/service-configurations/index.html
@@ -346,197 +346,30 @@
<nav class="toc">
<!-- <header><h4 class="nav__title"><i class="fa fa-file-text"></i> On This Page</h4></header> -->
<ul class="toc__menu" id="markdown-toc">
- <li><a href="#load-balancing-policy" id="markdown-toc-load-balancing-policy">Load Balancing Policy</a> <ul>
- <li><a href="#scenario" id="markdown-toc-scenario">Scenario</a></li>
- <li><a href="#configuration" id="markdown-toc-configuration">Configuration</a></li>
- <li><a href="#sample-code" id="markdown-toc-sample-code">Sample Code</a></li>
- </ul>
- </li>
- <li><a href="#customizing-routing-policies" id="markdown-toc-customizing-routing-policies">Customizing Routing Policies</a></li>
+ <li><a href="#load-balancing-policy" id="markdown-toc-load-balancing-policy">Load Balancing Policy</a></li>
<li><a href="#rate-limiting-policy" id="markdown-toc-rate-limiting-policy">Rate Limiting Policy</a> <ul>
- <li><a href="#scenario-1" id="markdown-toc-scenario-1">Scenario</a></li>
+ <li><a href="#scenario" id="markdown-toc-scenario">Scenario</a></li>
<li><a href="#precautions" id="markdown-toc-precautions">Precautions</a></li>
- <li><a href="#configuration-1" id="markdown-toc-configuration-1">Configuration</a></li>
+ <li><a href="#configuration" id="markdown-toc-configuration">Configuration</a></li>
</ul>
</li>
<li><a href="#fallback-policy" id="markdown-toc-fallback-policy">Fallback Policy</a> <ul>
<li><a href="#concept-description" id="markdown-toc-concept-description">Concept Description</a></li>
- <li><a href="#scenario-2" id="markdown-toc-scenario-2">Scenario</a></li>
- <li><a href="#configuration-2" id="markdown-toc-configuration-2">Configuration</a></li>
+ <li><a href="#scenario-1" id="markdown-toc-scenario-1">Scenario</a></li>
+ <li><a href="#configuration-1" id="markdown-toc-configuration-1">Configuration</a></li>
</ul>
</li>
- <li><a href="#sample-code-1" id="markdown-toc-sample-code-1">Sample Code</a></li>
+ <li><a href="#sample-code" id="markdown-toc-sample-code">Sample Code</a></li>
</ul>
</nav>
</aside>
<h2 id="load-balancing-policy">Load Balancing Policy</h2>
-<h3 id="scenario">Scenario</h3>
-
-<p> ServiceComb provides a Ribbon-based load balancing solution. You can configure a load balancing policy in the configuration file. Currently, a load balancing routing policy can be random, sequential, or based on response time weight.</p>
-
-<h3 id="configuration">Configuration</h3>
-
-<p> Load balancing policies are configured by setting the parameter <code class="highlighter-rouge">servicecomb.loadbalance.[MicroServiceName].[property name]</code> in the microservice.yaml fiel. If MicroServiceName is not set, the configuration is set for all microservices. Otherwise, the configuration is set for a specific microservice.</p>
-
-<p> <strong>Table 1 Configuration items of load balancing policy</strong></p>
-
-<table>
- <thead>
- <tr>
- <th style="text-align: left">Configuration Items</th>
- <th style="text-align: left">Default Value</th>
- <th style="text-align: left">Value Range</th>
- <th style="text-align: left">Mandatory</th>
- <th style="text-align: left">Description</th>
- <th style="text-align: left">Remarks</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td style="text-align: left">servicecomb.loadbalance.NFLoadBalancerRuleClassName</td>
- <td style="text-align: left">com.netflix.loadbalancer.RoundRobinRule</td>
- <td style="text-align: left">com.netflix.loadbalancer.RoundRobinRule（polling）com.netflix.loadbalancer.RandomRule（random）com.netflix.loadbalancer.WeightedResponseTimeRule（server response time weight）org.apache.servicecomb.loadbalance.SessionStickinessRule（session stickiness）</td>
- <td style="text-align: left">No</td>
- <td style="text-align: left">Specifiles the load balancing policy</td>
- <td style="text-align: left">-</td>
- </tr>
- <tr>
- <td style="text-align: left">servicecomb.loadbalance.SessionStickinessRule.sessionTimeoutInSeconds</td>
- <td style="text-align: left">30</td>
- <td style="text-align: left">Integer</td>
- <td style="text-align: left">No</td>
- <td style="text-align: left">Specifies the idle time of a client. If the idle time exceeds the set value, ServiceComb will select another server.</td>
- <td style="text-align: left">Currently, this parameter cannot be set for a certain microservice. For example, servicecomb.loadbalance.SessionStickinessRule.sessionTimeoutInSeconds cannot be set to servicecomb.loadbalance.DemoService.SessionStickinessRule.sessionTimeoutInSeconds</td>
- </tr>
- <tr>
- <td style="text-align: left">servicecomb.loadbalance.SessionStickinessRule.successiveFailedTimes</td>
- <td style="text-align: left">5</td>
- <td style="text-align: left">Integer</td>
- <td style="text-align: left">No</td>
- <td style="text-align: left">Specifies the number of failed requests from the client. If the number exceeds the set value, ServiceComb will switch to another server</td>
- <td style="text-align: left">Currently, this parameter cannot be set for a certain microservice.</td>
- </tr>
- <tr>
- <td style="text-align: left">servicecomb.loadbalance.retryEnabled</td>
- <td style="text-align: left">FALSE</td>
- <td style="text-align: left">Boolean</td>
- <td style="text-align: left">No</td>
- <td style="text-align: left">Specifies whether to call a service again when a exception is captured by the load balance.</td>
- <td style="text-align: left">-</td>
- </tr>
- <tr>
- <td style="text-align: left">servicecomb.loadbalance.retryOnNext</td>
- <td style="text-align: left">0</td>
- <td style="text-align: left">Integer</td>
- <td style="text-align: left">No</td>
- <td style="text-align: left">Specifies the number of attempts to connect to another server.</td>
- <td style="text-align: left">-</td>
- </tr>
- <tr>
- <td style="text-align: left">servicecomb.loadbalance.retryOnSame</td>
- <td style="text-align: left">0</td>
- <td style="text-align: left">Integer</td>
- <td style="text-align: left">No</td>
- <td style="text-align: left">Specifies the number of attempts to connect to the same server.</td>
- <td style="text-align: left">-</td>
- </tr>
- <tr>
- <td style="text-align: left">servicecomb.loadbalance.isolation.enabled</td>
- <td style="text-align: left">FALSE</td>
- <td style="text-align: left">Boolean</td>
- <td style="text-align: left">No</td>
- <td style="text-align: left">Specifies whether to enable faulty instance isolation.</td>
- <td style="text-align: left">-</td>
- </tr>
- <tr>
- <td style="text-align: left">servicecomb.loadbalance.isolation.enableRequestThreshold</td>
- <td style="text-align: left">20</td>
- <td style="text-align: left">Integer</td>
- <td style="text-align: left">No</td>
- <td style="text-align: left">Specifies the threshold number of instance calls. If this value is reached, isolation is enabled.</td>
- <td style="text-align: left">-</td>
- </tr>
- <tr>
- <td style="text-align: left">servicecomb.loadbalance.isolation.errorThresholdPercentage</td>
- <td style="text-align: left">20</td>
- <td style="text-align: left">Integer，(0,100]</td>
- <td style="text-align: left">No</td>
- <td style="text-align: left">Specifies the error percentage. Instance fault isolation is enabled when the set value is reached.</td>
- <td style="text-align: left">-</td>
- </tr>
- <tr>
- <td style="text-align: left">servicecomb.loadbalance.isolation.singleTestTime</td>
- <td style="text-align: left">10000</td>
- <td style="text-align: left">Integer</td>
- <td style="text-align: left">No</td>
- <td style="text-align: left">Specifies the duration of a faulty instance test on a single node.</td>
- <td style="text-align: left">This unit is ms.</td>
- </tr>
- <tr>
- <td style="text-align: left">servicecomb.loadbalance.transactionControl.policy</td>
- <td style="text-align: left">org.apache.servicecomb.loadbalance.filter.SimpleTransactionControlFilter</td>
- <td style="text-align: left">-</td>
- <td style="text-align: left">No</td>
- <td style="text-align: left">Specifies the offload policies for dynamic routing.</td>
- <td style="text-align: left">The framework provides simple offload mechanisms. You can also customize offload policies.</td>
- </tr>
- <tr>
- <td style="text-align: left">servicecomb.loadbalance.transactionControl.options</td>
- <td style="text-align: left">-</td>
- <td style="text-align: left">key/value pairs</td>
- <td style="text-align: left">No</td>
- <td style="text-align: left">Specifies the parameter configured for the SimpleTransactionControlFilter offload policy. You can add any filtration tag for this item.</td>
- <td style="text-align: left">-</td>
- </tr>
- </tbody>
-</table>
-
-<h3 id="sample-code">Sample Code</h3>
-
-<p> in the src/main/resources/microservice.yaml file, configure a load balancing policy.</p>
-
-<p> Configure a processing link：</p>
-
-<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">servicecomb</span><span class="pi">:</span>
- <span class="c1"># other configurations omitted</span>
- <span class="s">handler</span><span class="pi">:</span>
- <span class="s">chain</span><span class="pi">:</span>
- <span class="s">Consumer</span><span class="pi">:</span>
- <span class="s">default</span><span class="pi">:</span> <span class="s">loadbalance</span>
- <span class="c1"># other configurations omitted</span>
-</code></pre>
-</div>
-
-<p> Add a routing policy:</p>
-
-<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">servicecomb：</span>
- <span class="s"># other configurations omitted</span>
- <span class="s">loadbalance</span><span class="pi">:</span>
- <span class="s">NFLoadBalancerRuleClassName</span><span class="pi">:</span> <span class="s">com.netflix.loadbalancer.RoundRobinRule</span>
- <span class="c1"># other configurations omitted</span>
-</code></pre>
-</div>
-
-<h2 id="customizing-routing-policies">Customizing Routing Policies</h2>
-
-<p> Based on the routing policy framework provided by ServiceComb, you can program to customize routing policies as required. Perform the following steps:</p>
-
-<ul>
- <li>
- <p>Encode using the API method defined in the <code class="highlighter-rouge">com.netflix.loadbalancer.IRule</code> API. Encode in the public Server choose(Object key) method. LoadBalancerStats is a structure that encapsulates the running state of the load balancer. Determine on which instance the current routing request will be processed based on the running indexes of each instance by using the Server choose(Object key) method. Use method <code class="highlighter-rouge">org.apache [...]
- </li>
- <li>
- <p>Compile the developed policy and ensure that the generated class is under classpath.</p>
- </li>
- <li>
- <p>Use the software development kit(SDK) to configure the routing policy. Use AbcRule as a routing policy example. The configuration is as follows: <code class="highlighter-rouge">servicecomb.loadbalance.NFLoadBalancerRuleClassName=org.apache.servicecomb.ribbon.rule.AbcRule</code></p>
- </li>
-</ul>
+<p>The content of this page has been outdated, please refer to <a href="https://docs.servicecomb.io/java-chassis/en_US/references-handlers/loadbalance.html">Load Balancing</a></p>
<h2 id="rate-limiting-policy">Rate Limiting Policy</h2>
-<h3 id="scenario-1">Scenario</h3>
+<h3 id="scenario">Scenario</h3>
<p>Users at the provider end can use the rate limiting policy to limit the maximum number of requests sent from a specified microservice per second.</p>
@@ -548,7 +381,7 @@
<li>Traffic control is a microservice-level rather than process-level function.</li>
</ol>
-<h3 id="configuration-1">Configuration</h3>
+<h3 id="configuration">Configuration</h3>
<p> Rate limiting policies are configured in the microservice.yaml file. For related configuration items, see Table 2. To enable the rate limiting policy at the provider end, you also need to configure the rate limiting handler on the server in the processing chain and add dependencies in the pom.xml file.</p>
@@ -630,11 +463,11 @@
<p>During fallback, if M(the threshold) errors are detected in N requests, the consumer will no longer send requests and the fault tolerance mechanism will be enabled. The preceding fallback process is accepted in Netflix Hystrix and helps you configure the parameters. Obtain information about the parameter configuration at <a href="https://github.com/Netflix/Hystrix/wiki/Configuration">https://github.com/Netflix/Hystrix/wiki/Configuration</a>. Currently, ServiceComb provides two types [...]
-<h3 id="scenario-2">Scenario</h3>
+<h3 id="scenario-1">Scenario</h3>
<p>By configuring a fallback policy, you can handler microservice exceptions.</p>
-<h3 id="configuration-2">Configuration</h3>
+<h3 id="configuration-1">Configuration</h3>
<p> Configuration items of fallback policies are as follows:</p>
@@ -753,7 +586,7 @@
<p class="notice--warning"><strong>Caution:</strong> Be cautious when setting servicecomb.isolation.timeout.enabled to TRUE, All processes are asynchronously processed in the system, and any error value returned by an intermediate process because the set timeout duration is reached can cause failure of the follow-up processes. Therefore, you are advised to keep the default value FALSE for servicecomb.isolation.timeout.enabled. For timeout duration from the network aspect, you are advised [...]
-<h2 id="sample-code-1">Sample Code</h2>
+<h2 id="sample-code">Sample Code</h2>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">servicecomb</span><span class="pi">:</span>
<span class="s">handler</span><span class="pi">:</span>