You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by li...@apache.org on 2017/02/10 05:53:04 UTC
incubator-rocketmq-site git commit: Add priority note.
Repository: incubator-rocketmq-site
Updated Branches:
refs/heads/master bdd8b466f -> b66d708b7
Add priority note.
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/b66d708b
Tree: http://git-wip-us.apache.org/repos/asf/incubator-rocketmq-site/tree/b66d708b
Diff: http://git-wip-us.apache.org/repos/asf/incubator-rocketmq-site/diff/b66d708b
Branch: refs/heads/master
Commit: b66d708b737de9344dbb7bdb587c42030d76de01
Parents: bdd8b46
Author: Zhanhui Li <li...@apache.org>
Authored: Fri Feb 10 13:52:58 2017 +0800
Committer: Zhanhui Li <li...@apache.org>
Committed: Fri Feb 10 13:52:58 2017 +0800
----------------------------------------------------------------------
...-methods-to-feed-name-server-address-list.md | 29 ++++++++++++--------
1 file changed, 18 insertions(+), 11 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-rocketmq-site/blob/b66d708b/_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 f4c78b1..70984c9 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
@@ -20,7 +20,6 @@ provides four methods to achieve this goal.
1. Programmatic Way
For broker, we may specify `namesrvAddr=name-server-ip1:port;name-server-ip2:port` in broker configuration file.
- Alternatively, we may pass a parameter like `-n name-server-ip1:port;name-server-ip2:port` to `mqbroker` script.
For producers and consumers, we may feed name server address list to them as follows:
@@ -44,20 +43,22 @@ provides four methods to achieve this goal.
defaultMQAdminExt.setNamesrvAddr("name-server1-ip:port;name-server2-ip:port");`
-2. Environment Variable
+2. Java Options
- You can export `NAMESRV_ADDR` environment variable. Brokers and clients will examine and use its value if set.
+ Name server address list may also be fed to your application through specifying the sequel java option
+ `rocketmq.namesrv.addr` before launching.
-
-3. Java Options
+3. Environment Variable
- Similar to environment variable, you may specify the sequel java option `rocketmq.namesrv.addr` before launching your
- application.
+ 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.
+
-4. HTTP endpoint
+4. HTTP Endpoint
- If you do not specify name server address list using previously mentioned methods, Apache RocketMQ will periodically
- access the following HTTP end point to acquire and update name server address list.
+ If you do not specify name server address list using previously mentioned methods, Apache RocketMQ will access
+ the following HTTP end point to acquire and update name server address list every two minutes with initial delay of
+ ten seconds.
On default, the end point is:
@@ -68,4 +69,10 @@ provides four methods to achieve this goal.
This method is recommended because it gives you maximum flexibility, aka, you can dynamically add or
remove name server node without necessity of rebooting your brokers and clients according to your name servers'
- system load.
\ No newline at end of file
+ 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