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 2018/04/13 08:12:26 UTC
[incubator-servicecomb-website] branch asf-site updated (02d3895 ->
09d02d3)
This is an automated email from the ASF dual-hosted git repository.
ningjiang pushed a change to branch asf-site
in repository https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git.
from 02d3895 Push the website
add 7034419 add how to deploy service center in cluster mode (#60)
new ce2246e Merge branch 'master' into asf-site
new 09d02d3 Publish the website
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
_users/cn/setup-environment.md | 130 +++++++++++++++++++++-
_users/setup-environment.md | 133 ++++++++++++++++++++++-
content/cn/users/setup-environment/index.html | 148 ++++++++++++++++++++++++-
content/feed.xml | 2 +-
content/sitemap.xml | 4 +-
content/users/setup-environment/index.html | 151 +++++++++++++++++++++++++-
6 files changed, 548 insertions(+), 20 deletions(-)
--
To stop receiving notification emails like this one, please contact
ningjiang@apache.org.
[incubator-servicecomb-website] 01/02: Merge branch 'master' into
asf-site
Posted by ni...@apache.org.
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/incubator-servicecomb-website.git
commit ce2246eb87f4b6465a99e9b7d73d7116f4fb97c3
Merge: 02d3895 7034419
Author: Willem Jiang <ji...@huawei.com>
AuthorDate: Fri Apr 13 16:10:53 2018 +0800
Merge branch 'master' into asf-site
_users/cn/setup-environment.md | 130 +++++++++++++++++++++++++++++++++++++++-
_users/setup-environment.md | 133 +++++++++++++++++++++++++++++++++++++++--
2 files changed, 255 insertions(+), 8 deletions(-)
--
To stop receiving notification emails like this one, please contact
ningjiang@apache.org.
[incubator-servicecomb-website] 02/02: Publish the website
Posted by ni...@apache.org.
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/incubator-servicecomb-website.git
commit 09d02d3c60d54292e1510b4c6cabfaa55cc53490
Author: Willem Jiang <ji...@huawei.com>
AuthorDate: Fri Apr 13 16:12:09 2018 +0800
Publish the website
---
content/cn/users/setup-environment/index.html | 148 ++++++++++++++++++++++++-
content/feed.xml | 2 +-
content/sitemap.xml | 4 +-
content/users/setup-environment/index.html | 151 +++++++++++++++++++++++++-
4 files changed, 293 insertions(+), 12 deletions(-)
diff --git a/content/cn/users/setup-environment/index.html b/content/cn/users/setup-environment/index.html
index 78d8859..d7db46f 100644
--- a/content/cn/users/setup-environment/index.html
+++ b/content/cn/users/setup-environment/index.html
@@ -608,7 +608,7 @@
<meta itemprop="headline" content="环境配置">
<meta itemprop="description" content="环境配置">
- <meta itemprop="dateModified" content="September 03, 2017">
+ <meta itemprop="dateModified" content="April 13, 2018">
<div class="page__inner-wrap">
@@ -627,7 +627,11 @@
<!-- <header><h4 class="nav__title"><i class="fa fa-file-text"></i> 在本页上</h4></header> -->
<ul class="toc__menu" id="markdown-toc">
<li><a href="#安装java开发环境" id="markdown-toc-安装java开发环境">安装Java开发环境</a></li>
- <li><a href="#运行service-center" id="markdown-toc-运行service-center">运行<em>Service Center</em></a></li>
+ <li><a href="#运行-service-center" id="markdown-toc-运行-service-center">运行 Service Center</a> <ul>
+ <li><a href="#运行-stand-alone-service-center" id="markdown-toc-运行-stand-alone-service-center">运行 Stand-alone Service Center</a></li>
+ <li><a href="#运行-service-center-集群" id="markdown-toc-运行-service-center-集群">运行 Service Center 集群</a></li>
+ </ul>
+ </li>
</ul>
</nav>
@@ -650,8 +654,9 @@
</li>
</ul>
-<h2 id="运行service-center">运行<em>Service Center</em></h2>
-<p>运行Service Center有以下两种方式:</p>
+<h2 id="运行-service-center">运行 Service Center</h2>
+<h3 id="运行-stand-alone-service-center">运行 Stand-alone Service Center</h3>
+<p>运行Stand-alone Service Center有以下两种方式:</p>
<ol>
<li>
@@ -702,6 +707,141 @@ docker run -d -p 30100:30100 servicecomb/service-center:latest
<p class="notice--warning"><strong>注意事项：</strong> 服务注册中心运行后绑定的IP为：<em>http://127.0.0.1:30100</em>。<br />
如使用Docker Toolbox，可通过 <code class="highlighter-rouge">docker-machine ip</code> 获取服务绑定IP地址。</p>
+<h3 id="运行-service-center-集群">运行 Service Center 集群</h3>
+<p>Service Center是一个无状态的应用因此它很容易以集群的模式部署提供HA。</p>
+
+<p>它依赖<a href="https://github.com/coreos/etcd">etcd</a>存储微服务的信息，etcd既支持standalone模式运行也支持<a href="https://coreos.com/etcd/docs/latest/op-guide/clustering.html">集群模式</a>运行。</p>
+
+<p>提示：我们强烈推荐etcd以集群模式运行，这样才能从整体上保证Service Center的HA能力；另外在这篇<a href="https://coreos.com/etcd/docs/latest/op-guide/runtime-configuration.html">文档</a>中我们可以了解到etcd需要部署至少三个节点才能够避免Majority Failure。</p>
+
+<p>部署了standalone或集群etcd后，你可以按下面的步骤部署Service Center集群，我们以在两台VM上各部署一个Service Center实例为例：</p>
+
+<table>
+ <thead>
+ <tr>
+ <th style="text-align: center">Name</th>
+ <th style="text-align: center">Address</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td style="text-align: center">VM1</td>
+ <td style="text-align: center">10.12.0.1</td>
+ </tr>
+ <tr>
+ <td style="text-align: center">VM2</td>
+ <td style="text-align: center">10.12.0.2</td>
+ </tr>
+ </tbody>
+</table>
+
+<p>我们假定你的etcd运行在http://10.12.0.4:2379 上：</p>
+
+<h5 id="第一步">第一步</h5>
+<p>在所有的VM上从<a href="https://github.com/apache/incubator-servicecomb-service-center/releases">ServiceComb官网</a>下载最新版本的Service Center并解压：</p>
+
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code>tar -xvf service-center-X.X.X-linux-amd64.tar.gz
+</code></pre>
+</div>
+
+<p>提示：请不要按stand-alone提示的方式执行start-service-center.sh，因为这样会启动内置的etcd。</p>
+
+<h5 id="第二步">第二步</h5>
+<p>编辑ServcieComb的配置文件，修改ip/port以及etcd地址：</p>
+<h6 id="vm1">VM1</h6>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code>vi conf/app.conf
+</code></pre>
+</div>
+
+<p>修改下面的配置 :</p>
+<div class="language-text highlighter-rouge"><pre class="highlight"><code>httpaddr = 10.12.0.1
+manager_cluster = "10.12.0.4:2379"
+</code></pre>
+</div>
+
+<p>然后启动Service Center :</p>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code>./service-center
+</code></pre>
+</div>
+
+<h6 id="vm2">VM2</h6>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code>vi conf/app.conf
+</code></pre>
+</div>
+
+<p>修改下面的配置 :</p>
+<div class="language-text highlighter-rouge"><pre class="highlight"><code>httpaddr = 10.12.0.2
+manager_cluster = "10.12.0.4:2379"
+</code></pre>
+</div>
+
+<p>然后启动Service Center :</p>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code>./service-center
+</code></pre>
+</div>
+
+<p>提示：在<code class="highlighter-rouge">manger_cluster</code>配置中你可以填写多个在etcd群集中的etcd实例地址：</p>
+<div class="highlighter-rouge"><pre class="highlight"><code>manager_cluster= "10.12.0.4:2379,10.12.0.X:2379,10.12.0.X:2379"
+</code></pre>
+</div>
+
+<h5 id="第三步">第三步</h5>
+<p>验证你部署完毕的Service Center实例 :</p>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code>curl http://10.12.0.1:30101/v4/default/registry/health
+</code></pre>
+</div>
+<p>将会返回下面的内容 :</p>
+<div class="language-json highlighter-rouge"><pre class="highlight"><code><span class="p">{</span><span class="w">
+ </span><span class="nt">"instances"</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="w">
+ </span><span class="p">{</span><span class="w">
+ </span><span class="nt">"instanceId"</span><span class="p">:</span><span class="w"> </span><span class="s2">"d6e9e976f9df11e7a72b286ed488ff9f"</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"serviceId"</span><span class="p">:</span><span class="w"> </span><span class="s2">"d6e99f4cf9df11e7a72b286ed488ff9f"</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"endpoints"</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="w">
+ </span><span class="s2">"rest://10.12.0.1:30100"</span><span class="w">
+ </span><span class="p">],</span><span class="w">
+ </span><span class="nt">"hostName"</span><span class="p">:</span><span class="w"> </span><span class="s2">"service_center_10_12_0_1"</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"status"</span><span class="p">:</span><span class="w"> </span><span class="s2">"UP"</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"healthCheck"</span><span class="p">:</span><span class="w"> </span><span class="p">{</span><span class="w">
+ </span><span class="nt">"mode"</span><span class="p">:</span><span class="w"> </span><span class="s2">"push"</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"interval"</span><span class="p">:</span><span class="w"> </span><span class="mi">30</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"times"</span><span class="p">:</span><span class="w"> </span><span class="mi">3</span><span class="w">
+ </span><span class="p">},</span><span class="w">
+ </span><span class="nt">"timestamp"</span><span class="p">:</span><span class="w"> </span><span class="s2">"1516012543"</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"modTimestamp"</span><span class="p">:</span><span class="w"> </span><span class="s2">"1516012543"</span><span class="w">
+ </span><span class="p">},</span><span class="w">
+ </span><span class="p">{</span><span class="w">
+ </span><span class="nt">"instanceId"</span><span class="p">:</span><span class="w"> </span><span class="s2">"16d4cb35f9e011e7a58a286ed488ff9f"</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"serviceId"</span><span class="p">:</span><span class="w"> </span><span class="s2">"d6e99f4cf9df11e7a72b286ed488ff9f"</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"endpoints"</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="w">
+ </span><span class="s2">"rest://10.12.0.2:30100"</span><span class="w">
+ </span><span class="p">],</span><span class="w">
+ </span><span class="nt">"hostName"</span><span class="p">:</span><span class="w"> </span><span class="s2">"service_center_10_12_0_2"</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"status"</span><span class="p">:</span><span class="w"> </span><span class="s2">"UP"</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"healthCheck"</span><span class="p">:</span><span class="w"> </span><span class="p">{</span><span class="w">
+ </span><span class="nt">"mode"</span><span class="p">:</span><span class="w"> </span><span class="s2">"push"</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"interval"</span><span class="p">:</span><span class="w"> </span><span class="mi">30</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"times"</span><span class="p">:</span><span class="w"> </span><span class="mi">3</span><span class="w">
+ </span><span class="p">},</span><span class="w">
+ </span><span class="nt">"timestamp"</span><span class="p">:</span><span class="w"> </span><span class="s2">"1516012650"</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"modTimestamp"</span><span class="p">:</span><span class="w"> </span><span class="s2">"1516012650"</span><span class="w">
+ </span><span class="p">}</span><span class="w">
+ </span><span class="p">]</span><span class="w">
+</span><span class="p">}</span><span class="w">
+</span></code></pre>
+</div>
+
+<p>我们可以看到Service Center能够自动发现所有正在集群中运行的实例，<a href="https://github.com/apache/incubator-servicecomb-java-chassis">Java-Chassis SDK</a>将使用这个特性至少找到一个Service Center实例。</p>
+
+<p>在你的microservice.yaml中你可以填写一个或多个Service Center实例，如果<a href="https://github.com/apache/incubator-servicecomb-java-chassis">Java-Chassis SDK</a>发现配置的第一个地址（实例）失败，它将会自动使用下一个地址（实例）：</p>
+<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">cse</span><span class="pi">:</span>
+ <span class="s">service</span><span class="pi">:</span>
+ <span class="s">registry</span><span class="pi">:</span>
+ <span class="s">address</span><span class="pi">:</span> <span class="s2">"</span><span class="s">http://10.12.0.1:30100,http://10.12.0.2:30100"</span>
+ <span class="s">autodiscovery</span><span class="pi">:</span> <span class="s">true</span>
+</code></pre>
+</div>
+<p>上面的例子里包含了我们已经配置好的两个Service Center实例。</p>
+
</section>
diff --git a/content/feed.xml b/content/feed.xml
index 28fbfa4..b85e794 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>2018-04-09T14:42:35+08:00</updated><id>/</id><title type="html">Apache ServiceComb (incubating)</title><subtitle>The homepage of ServiceComb</subtitle><author><name>{"name"=>nil, "avatar"=> [...]
+<?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>2018-04-13T16:11:13+08:00</updated><id>/</id><title type="html">Apache ServiceComb (incubating)</title><subtitle>The homepage of ServiceComb</subtitle><author><name>{"name"=>nil, "avatar"=> [...]
<ul>
<li><strong>嵌套调用</strong>。如网上购物时，会依次经过下单、支付服务和第三方支付这几个子事务，其中，下单依赖于支付服务的返回状态，而支付服务也包含了多种可选的支付方式，并依赖于具体支付方式返回的结果。通过Saga，可以清晰地看到一个完整事务中各个服务之间的关系，在异常时也能快速定位出现问题的子事务。</li>
diff --git a/content/sitemap.xml b/content/sitemap.xml
index 6d9d7ff..e55ebfb 100644
--- a/content/sitemap.xml
+++ b/content/sitemap.xml
@@ -554,11 +554,11 @@
</url>
<url>
<loc>/users/setup-environment/</loc>
-<lastmod>2017-09-03T22:01:43+08:00</lastmod>
+<lastmod>2018-04-13T22:01:43+08:00</lastmod>
</url>
<url>
<loc>/cn/users/setup-environment/</loc>
-<lastmod>2017-09-03T22:01:43+08:00</lastmod>
+<lastmod>2018-04-13T22:01:43+08:00</lastmod>
</url>
<url>
<loc>/sitemap/</loc>
diff --git a/content/users/setup-environment/index.html b/content/users/setup-environment/index.html
index 9ab1f36..f5e0f3c 100644
--- a/content/users/setup-environment/index.html
+++ b/content/users/setup-environment/index.html
@@ -591,7 +591,7 @@
<meta itemprop="headline" content="Setup Environment">
<meta itemprop="description" content="Setup Environment">
- <meta itemprop="dateModified" content="September 03, 2017">
+ <meta itemprop="dateModified" content="April 13, 2018">
<div class="page__inner-wrap">
@@ -610,7 +610,11 @@
<!-- <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="#setup-local-java-develop-environment" id="markdown-toc-setup-local-java-develop-environment">Setup Local Java Develop Environment</a></li>
- <li><a href="#starting-local-service-center" id="markdown-toc-starting-local-service-center">Starting Local <em>Service Center</em></a></li>
+ <li><a href="#starting-service-center" id="markdown-toc-starting-service-center">Starting Service Center</a> <ul>
+ <li><a href="#starting-stand-alone-service-center" id="markdown-toc-starting-stand-alone-service-center">Starting Stand-alone Service Center</a></li>
+ <li><a href="#starting-clustered-service-center" id="markdown-toc-starting-clustered-service-center">Starting Clustered Service Center</a></li>
+ </ul>
+ </li>
</ul>
</nav>
@@ -633,8 +637,9 @@
</li>
</ul>
-<h2 id="starting-local-service-center">Starting Local <em>Service Center</em></h2>
-<p>There are two ways to start a service center service:</p>
+<h2 id="starting-service-center">Starting Service Center</h2>
+<h3 id="starting-stand-alone-service-center">Starting Stand-alone Service Center</h3>
+<p>There are two ways to start a stand-alone service center service:</p>
<ol>
<li>
@@ -653,7 +658,7 @@
<li>Start Local ServiceCenter from <strong>start-service-center.bat</strong> file</li>
</ol>
</div>
-<div id="linux" class="tab-pane fade">
+ <div id="linux" class="tab-pane fade">
<ol>
<li>Download and Decompress command:
<div class="language-bash highlighter-rouge"><pre class="highlight"><code>wget http://apache.org/dyn/closer.cgi/incubator/servicecomb/incubator-servicecomb-service-center/1.0.0-m1/apache-servicecomb-incubating-service-center-1.0.0-m1-linux-amd64.tar.gz
@@ -685,6 +690,142 @@ docker run -d -p 30100:30100 servicecomb/service-center:latest
<p class="notice--warning"><strong>NOTE：</strong> Running Service Center will bind on: <em>http://127.0.0.1:30100</em>。<br />
If using Docker Toolbox，command <code class="highlighter-rouge">docker-machine ip</code> can be used to get binded IP address.</p>
+<h3 id="starting-clustered-service-center">Starting Clustered Service Center</h3>
+<p>As Service-center is a stateless application so it can be seamlessly deployed in cluster mode to achieve HA.</p>
+
+<p>SC is dependent on the <a href="https://github.com/coreos/etcd">etcd</a> to store the micro-services information so you can opt for running etcd standalone or in <a href="https://coreos.com/etcd/docs/latest/op-guide/runtime-configuration.html">cluster</a> mode.</p>
+
+<p>Notice: We strongly recommend running etcd in cluster mode in order to get the perfect HA ability. In this <a href="https://coreos.com/etcd/docs/latest/op-guide/runtime-configuration.html">document</a> we can know it is highly recommended to always have a cluster size greater than two in production in order to prevent Majority Failure.</p>
+
+<p>Once you are done with installing the etcd either in cluster or standalone mode then you can follow the below steps to run the Service-Center.</p>
+
+<p>Let’s assume you want to install 2 instances of Service-Center on VM with following details</p>
+
+<table>
+ <thead>
+ <tr>
+ <th style="text-align: center">Name</th>
+ <th style="text-align: center">Address</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td style="text-align: center">VM1</td>
+ <td style="text-align: center">10.12.0.1</td>
+ </tr>
+ <tr>
+ <td style="text-align: center">VM2</td>
+ <td style="text-align: center">10.12.0.2</td>
+ </tr>
+ </tbody>
+</table>
+
+<p>Here we assume your etcd is running on http://10.12.0.4:2379 (you can follow <a href="https://github.com/coreos/etcd/blob/master/Documentation/op-guide/container.md">this</a> guide to install etcd in cluster mode.)</p>
+
+<h5 id="step-1">Step 1</h5>
+<p>Download the SC release from <a href="https://github.com/apache/incubator-servicecomb-service-center/releases">here</a> on all the VM’s.</p>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code>tar -xvf service-center-X.X.X-linux-amd64.tar.gz
+</code></pre>
+</div>
+
+<p>Note: Please don’t run start-service-center.sh as it will also start the built-in etcd.</p>
+
+<h5 id="step-2">Step 2</h5>
+<p>Edit the configuration of the ip/port on which SC will run and etcd ip</p>
+<h6 id="vm1">VM1</h6>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code>vi conf/app.conf
+</code></pre>
+</div>
+
+<p>Replace the below values :</p>
+<div class="language-text highlighter-rouge"><pre class="highlight"><code>httpaddr = 10.12.0.1
+manager_cluster = "10.12.0.4:2379"
+</code></pre>
+</div>
+
+<p>Then start the Service-center :</p>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code>./service-center
+</code></pre>
+</div>
+
+<h6 id="vm2">VM2</h6>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code>vi conf/app.conf
+</code></pre>
+</div>
+
+<p>Replace the below values :</p>
+<div class="language-text highlighter-rouge"><pre class="highlight"><code>httpaddr = 10.12.0.2
+manager_cluster = "10.12.0.4:2379"
+</code></pre>
+</div>
+
+<p>Then start the Service-center :</p>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code>./service-center
+</code></pre>
+</div>
+
+<p>Note: In <code class="highlighter-rouge">manger_cluster</code> you can put the multiple instances of etcd in the cluster like :</p>
+<div class="highlighter-rouge"><pre class="highlight"><code>manager_cluster= "10.12.0.4:2379,10.12.0.X:2379,10.12.0.X:2379"
+</code></pre>
+</div>
+
+<h5 id="step-3">Step 3</h5>
+<p>Verify your instances via :</p>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code>curl http://10.12.0.1:30101/v4/default/registry/health
+</code></pre>
+</div>
+<p>Will return :</p>
+<div class="language-json highlighter-rouge"><pre class="highlight"><code><span class="p">{</span><span class="w">
+ </span><span class="nt">"instances"</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="w">
+ </span><span class="p">{</span><span class="w">
+ </span><span class="nt">"instanceId"</span><span class="p">:</span><span class="w"> </span><span class="s2">"d6e9e976f9df11e7a72b286ed488ff9f"</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"serviceId"</span><span class="p">:</span><span class="w"> </span><span class="s2">"d6e99f4cf9df11e7a72b286ed488ff9f"</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"endpoints"</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="w">
+ </span><span class="s2">"rest://10.12.0.1:30100"</span><span class="w">
+ </span><span class="p">],</span><span class="w">
+ </span><span class="nt">"hostName"</span><span class="p">:</span><span class="w"> </span><span class="s2">"service_center_10_12_0_1"</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"status"</span><span class="p">:</span><span class="w"> </span><span class="s2">"UP"</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"healthCheck"</span><span class="p">:</span><span class="w"> </span><span class="p">{</span><span class="w">
+ </span><span class="nt">"mode"</span><span class="p">:</span><span class="w"> </span><span class="s2">"push"</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"interval"</span><span class="p">:</span><span class="w"> </span><span class="mi">30</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"times"</span><span class="p">:</span><span class="w"> </span><span class="mi">3</span><span class="w">
+ </span><span class="p">},</span><span class="w">
+ </span><span class="nt">"timestamp"</span><span class="p">:</span><span class="w"> </span><span class="s2">"1516012543"</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"modTimestamp"</span><span class="p">:</span><span class="w"> </span><span class="s2">"1516012543"</span><span class="w">
+ </span><span class="p">},</span><span class="w">
+ </span><span class="p">{</span><span class="w">
+ </span><span class="nt">"instanceId"</span><span class="p">:</span><span class="w"> </span><span class="s2">"16d4cb35f9e011e7a58a286ed488ff9f"</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"serviceId"</span><span class="p">:</span><span class="w"> </span><span class="s2">"d6e99f4cf9df11e7a72b286ed488ff9f"</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"endpoints"</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="w">
+ </span><span class="s2">"rest://10.12.0.2:30100"</span><span class="w">
+ </span><span class="p">],</span><span class="w">
+ </span><span class="nt">"hostName"</span><span class="p">:</span><span class="w"> </span><span class="s2">"service_center_10_12_0_2"</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"status"</span><span class="p">:</span><span class="w"> </span><span class="s2">"UP"</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"healthCheck"</span><span class="p">:</span><span class="w"> </span><span class="p">{</span><span class="w">
+ </span><span class="nt">"mode"</span><span class="p">:</span><span class="w"> </span><span class="s2">"push"</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"interval"</span><span class="p">:</span><span class="w"> </span><span class="mi">30</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"times"</span><span class="p">:</span><span class="w"> </span><span class="mi">3</span><span class="w">
+ </span><span class="p">},</span><span class="w">
+ </span><span class="nt">"timestamp"</span><span class="p">:</span><span class="w"> </span><span class="s2">"1516012650"</span><span class="p">,</span><span class="w">
+ </span><span class="nt">"modTimestamp"</span><span class="p">:</span><span class="w"> </span><span class="s2">"1516012650"</span><span class="w">
+ </span><span class="p">}</span><span class="w">
+ </span><span class="p">]</span><span class="w">
+</span><span class="p">}</span><span class="w">
+</span></code></pre>
+</div>
+
+<p>As we can see here the Service-Center can auto-discover all the instances of the Service-Center running in cluster, this auto-discovery feature is used by the <a href="https://github.com/apache/incubator-servicecomb-java-chassis">Java-Chassis SDK</a> to auto-discover all the instances of the Service-Center by knowing at least one IP of Service-Center running in cluster.</p>
+
+<p>In your microservice.yaml you can provide the SC IP of both the instance or any one instance, sdk can auto-discover other instances and use the other instances to get microservice details in case of failure of the first one.</p>
+<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">cse</span><span class="pi">:</span>
+ <span class="s">service</span><span class="pi">:</span>
+ <span class="s">registry</span><span class="pi">:</span>
+ <span class="s">address</span><span class="pi">:</span> <span class="s2">"</span><span class="s">http://10.12.0.1:30100,http://10.12.0.2:30100"</span>
+ <span class="s">autodiscovery</span><span class="pi">:</span> <span class="s">true</span>
+</code></pre>
+</div>
+<p>In this case sdk will be able to discover all the instances of SC in cluster.</p>
+
</section>
--
To stop receiving notification emails like this one, please contact
ningjiang@apache.org.