rocketmq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From lizhan...@apache.org
Subject [1/2] incubator-rocketmq-site git commit: Changes to the text on specifying name server list.
Date Fri, 10 Feb 2017 08:26:47 GMT
Repository: incubator-rocketmq-site
Updated Branches:
  refs/heads/master b66d708b7 -> ef72b0044


Changes to the text on specifying name server list.


Project: http://git-wip-us.apache.org/repos/asf/incubator-rocketmq-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-rocketmq-site/commit/c706e003
Tree: http://git-wip-us.apache.org/repos/asf/incubator-rocketmq-site/tree/c706e003
Diff: http://git-wip-us.apache.org/repos/asf/incubator-rocketmq-site/diff/c706e003

Branch: refs/heads/master
Commit: c706e003dd8dc8b4a222bbfc4b25efca502e4527
Parents: b66d708
Author: shtykh_roman <rshtykh@yahoo.com>
Authored: Fri Feb 10 15:57:35 2017 +0900
Committer: Zhanhui Li <lizhanhui@apache.org>
Committed: Fri Feb 10 16:07:44 2017 +0800

----------------------------------------------------------------------
 ...-methods-to-feed-name-server-address-list.md | 23 ++++++++++----------
 1 file changed, 11 insertions(+), 12 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-rocketmq-site/blob/c706e003/_posts/2017-02-10-four-methods-to-feed-name-server-address-list.md
----------------------------------------------------------------------
diff --git a/_posts/2017-02-10-four-methods-to-feed-name-server-address-list.md b/_posts/2017-02-10-four-methods-to-feed-name-server-address-list.md
index 70984c9..aa27066 100644
--- a/_posts/2017-02-10-four-methods-to-feed-name-server-address-list.md
+++ b/_posts/2017-02-10-four-methods-to-feed-name-server-address-list.md
@@ -7,15 +7,15 @@ tags:
   - Name Server
 ---
 
-Apache RocketMQ is a distributed system that each components should be properly coordinated
to work smoothly. Name 
-servers are designed to take much of this responsibility through managing topic route information.
+In Apache RocketMQ, name servers are designed to coordinate each component of the distributed
system
+and take much of the responsibility for managing topic route information.
 
-The management, roughly speaking, consists two parts. The first one is that brokers report
to name servers on meta data
-of themselves and topics they have. The second is serving clients, including producer, consumer
and command line
- executables these meta data.
+The management, roughly speaking, consists two parts
+- Brokers send their meta data to name servers and report on topics they have.
+- Name servers are serving clients, including producers, consumers and command line clients
with the freshest routing information.
 
-As a result, before launching brokers and clients, we need to feed name server address list
to them. Apache RocketMQ 
-provides four methods to achieve this goal.
+Therefore, before launching brokers and clients, we need to tell them how to reach name servers
by feeding them with a name server address list.
+In Apache RocketMQ, this can be done in four ways.
 
 1. Programmatic Way
 
@@ -50,8 +50,7 @@ provides four methods to achieve this goal.
     
 3. Environment Variable
 
-   A third method is via environment variable: you can export `NAMESRV_ADDR` environment
variable. Brokers and clients 
-   will examine and use its value if set.
+   You can export `NAMESRV_ADDR` environment variable. Brokers and clients will examine and
use its value if set.
     
     
 4. HTTP Endpoint
@@ -67,12 +66,12 @@ provides four methods to achieve this goal.
     You may override `jmenv.tbsite.net` by this java option: `rocketmq.namesrv.domain`,
     You may also override `nsaddr` part by this java option: `rocketmq.namesrv.domain.subgroup`
     
-    This method is recommended because it gives you maximum flexibility, aka, you can dynamically
add or 
+    This method is recommended because it gives you maximum flexibility -- you can dynamically
add or 
     remove name server node without necessity of rebooting your brokers and clients according
to your name servers'
     system load.
      
      
 *  Priority
 
-    Methods introduced first take precedence over the latter, namely,
-    Programmatic Way > Java Options > Environment Variable > HTTP Endpoint
\ No newline at end of file
+    Methods introduced first take precedence over the latter, namely, <br>
+    `Programmatic Way > Java Options > Environment Variable > HTTP Endpoint`
\ No newline at end of file


Mime
View raw message