You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by hu...@apache.org on 2021/08/11 09:51:28 UTC
[rocketmq-site] branch asf-site updated: prepare to release
rocketmq 4.9.1 version
This is an automated email from the ASF dual-hosted git repository.
huzongtang pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/rocketmq-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 1f8c918 prepare to release rocketmq 4.9.1 version
1f8c918 is described below
commit 1f8c918b07844bb688bee5674f2edd8a744e6e32
Author: zongtanghu <zo...@gmail.com>
AuthorDate: Wed Aug 11 17:51:08 2021 +0800
prepare to release rocketmq 4.9.1 version
---
content/about/contact/index.html | 2 +-
content/about/rewards/index.html | 2 +-
content/about/team/index.html | 2 +-
content/archive-layout-with-content/index.html | 8 +--
content/docs/batch-example/index.html | 2 +-
content/docs/best-practice-broker/index.html | 2 +-
content/docs/best-practice-consumer/index.html | 2 +-
content/docs/best-practice-namesvr/index.html | 18 +++---
content/docs/best-practice-producer/index.html | 2 +-
content/docs/broadcast-example/index.html | 2 +-
content/docs/cli-admin-tool/index.html | 10 ++--
content/docs/cluster-deployment/index.html | 18 +++---
content/docs/code-guidelines/index.html | 2 +-
content/docs/core-concept/index.html | 2 +-
content/docs/create-pull-request/index.html | 26 ++++----
content/docs/documentation/index.html | 4 +-
content/docs/faq/index.html | 4 +-
content/docs/filter-by-sql92-example/index.html | 20 +++----
content/docs/how-to-contribute/index.html | 2 +-
content/docs/logappender-example/index.html | 10 ++--
content/docs/motivation/index.html | 2 +-
content/docs/openmessaging-example/index.html | 2 +-
content/docs/order-example/index.html | 2 +-
content/docs/pull-request/index.html | 36 +++++------
content/docs/quick-start/index.html | 6 +-
content/docs/release-manual.html | 34 +++++------
content/docs/rmq-arc/index.html | 8 +--
content/docs/rmq-deployment/index.html | 2 +-
content/docs/roadmap/index.html | 4 +-
content/docs/schedule-example/index.html | 2 +-
content/docs/simple-example/index.html | 2 +-
content/docs/system-config/index.html | 18 +++---
content/docs/transaction-example/index.html | 2 +-
content/dowloading/releases/index.html | 2 +-
content/feed.xml | 22 +++----
.../index.html | 2 +-
.../index.html | 38 ++++++------
.../index.html | 32 +++++-----
content/sitemap.xml | 70 +++++++++++-----------
39 files changed, 213 insertions(+), 213 deletions(-)
diff --git a/content/about/contact/index.html b/content/about/contact/index.html
index d95c025..3b937e5 100644
--- a/content/about/contact/index.html
+++ b/content/about/contact/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
diff --git a/content/about/rewards/index.html b/content/about/rewards/index.html
index 369b804..f7c9296 100644
--- a/content/about/rewards/index.html
+++ b/content/about/rewards/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
diff --git a/content/about/team/index.html b/content/about/team/index.html
index 499946c..2829a29 100644
--- a/content/about/team/index.html
+++ b/content/about/team/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
diff --git a/content/archive-layout-with-content/index.html b/content/archive-layout-with-content/index.html
index c38aa25..528777b 100644
--- a/content/archive-layout-with-content/index.html
+++ b/content/archive-layout-with-content/index.html
@@ -450,7 +450,7 @@
<h2 id="buttons">Buttons</h2>
-<p>Make any link standout more when applying the <code class="highlighter-rouge">.btn</code> class.</p>
+<p>Make any link standout more when applying the <code class="language-plaintext highlighter-rouge">.btn</code> class.</p>
<div class="language-html highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nt"><a</span> <span class="na">href=</span><span class="s">"#"</span> <span class="na">class=</span><span class="s">"btn--success"</span><span class="nt">></span>Success Button<span class="nt"></a></span>
</code></pre></div></div>
@@ -485,7 +485,7 @@
<h2 id="notices">Notices</h2>
-<p class="notice"><strong>Watch out!</strong> You can also add notices by appending <code class="highlighter-rouge">{: .notice}</code> to a paragraph.</p>
+<p class="notice"><strong>Watch out!</strong> You can also add notices by appending <code class="language-plaintext highlighter-rouge">{: .notice}</code> to a paragraph.</p>
<h2 id="html-tags">HTML Tags</h2>
@@ -509,7 +509,7 @@
<h3 id="code-tag">Code Tag</h3>
-<p>You will learn later on in these tests that <code class="highlighter-rouge">word-wrap: break-word;</code> will be your best friend.</p>
+<p>You will learn later on in these tests that <code class="language-plaintext highlighter-rouge">word-wrap: break-word;</code> will be your best friend.</p>
<h3 id="strike-tag">Strike Tag</h3>
@@ -525,7 +525,7 @@
<h3 id="keyboard-tag">Keyboard Tag</h3>
-<p>This scarcely known tag emulates <kbd>keyboard text</kbd>, which is usually styled like the <code class="highlighter-rouge"><code></code> tag.</p>
+<p>This scarcely known tag emulates <kbd>keyboard text</kbd>, which is usually styled like the <code class="language-plaintext highlighter-rouge"><code></code> tag.</p>
<h3 id="preformatted-tag">Preformatted Tag</h3>
diff --git a/content/docs/batch-example/index.html b/content/docs/batch-example/index.html
index 9253c12..71a1c66 100644
--- a/content/docs/batch-example/index.html
+++ b/content/docs/batch-example/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
diff --git a/content/docs/best-practice-broker/index.html b/content/docs/best-practice-broker/index.html
index b7872a0..a59e40b 100644
--- a/content/docs/best-practice-broker/index.html
+++ b/content/docs/best-practice-broker/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
diff --git a/content/docs/best-practice-consumer/index.html b/content/docs/best-practice-consumer/index.html
index 81f5233..cf50536 100644
--- a/content/docs/best-practice-consumer/index.html
+++ b/content/docs/best-practice-consumer/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
diff --git a/content/docs/best-practice-namesvr/index.html b/content/docs/best-practice-namesvr/index.html
index 41f8685..bd542c2 100644
--- a/content/docs/best-practice-namesvr/index.html
+++ b/content/docs/best-practice-namesvr/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
@@ -488,7 +488,7 @@ In Apache RocketMQ, this can be done in four ways.</p>
<h2 id="programmatic-way">Programmatic Way</h2>
-<p>For brokers, we can specify <code class="highlighter-rouge">namesrvAddr=name-server-ip1:port;name-server-ip2:port</code> in broker configuration file.</p>
+<p>For brokers, we can specify <code class="language-plaintext highlighter-rouge">namesrvAddr=name-server-ip1:port;name-server-ip2:port</code> in broker configuration file.</p>
<p>For producers and consumers, we can feed name server address list to them as follows:</p>
@@ -505,7 +505,7 @@ In Apache RocketMQ, this can be done in four ways.</p>
</code></pre></div></div>
<p>A simple example is:
-<code class="highlighter-rouge">sh mqadmin -n localhost:9876 clusterList</code>
+<code class="language-plaintext highlighter-rouge">sh mqadmin -n localhost:9876 clusterList</code>
assuming to query cluster info on the name server node.</p>
<p>If you have integrated admin tool into your own dashboard, you can:</p>
@@ -517,11 +517,11 @@ assuming to query cluster info on the name server node.</p>
<h2 id="java-options">Java Options</h2>
<p>Name server address list may also be fed to your application through specifying the sequel java option
-<code class="highlighter-rouge">rocketmq.namesrv.addr</code> before launching.</p>
+<code class="language-plaintext highlighter-rouge">rocketmq.namesrv.addr</code> before launching.</p>
<h2 id="environment-variable">Environment Variable</h2>
-<p>You can export <code class="highlighter-rouge">NAMESRV_ADDR</code> environment variable. Brokers and clients will examine and use its value if set.</p>
+<p>You can export <code class="language-plaintext highlighter-rouge">NAMESRV_ADDR</code> environment variable. Brokers and clients will examine and use its value if set.</p>
<h2 id="http-endpoint">HTTP Endpoint</h2>
@@ -531,10 +531,10 @@ assuming to query cluster info on the name server node.</p>
<p>By default, the end point is:</p>
-<p><code class="highlighter-rouge">http://jmenv.tbsite.net:8080/rocketmq/nsaddr</code></p>
+<p><code class="language-plaintext highlighter-rouge">http://jmenv.tbsite.net:8080/rocketmq/nsaddr</code></p>
-<p>You may override <code class="highlighter-rouge">jmenv.tbsite.net</code> using this Java option: <code class="highlighter-rouge">rocketmq.namesrv.domain</code>,
-You may also override <code class="highlighter-rouge">nsaddr</code> part using this Java option: <code class="highlighter-rouge">rocketmq.namesrv.domain.subgroup</code></p>
+<p>You may override <code class="language-plaintext highlighter-rouge">jmenv.tbsite.net</code> using this Java option: <code class="language-plaintext highlighter-rouge">rocketmq.namesrv.domain</code>,
+You may also override <code class="language-plaintext highlighter-rouge">nsaddr</code> part using this Java option: <code class="language-plaintext highlighter-rouge">rocketmq.namesrv.domain.subgroup</code></p>
<p>If you are running Apache RocketMQ in production, this method is recommended because it gives you maximum flexibility
– you can dynamically add or remove name server nodes without necessity of rebooting your brokers and clients
@@ -543,7 +543,7 @@ You may also override <code class="highlighter-rouge">nsaddr</code> part using t
<h2 id="priority">Priority</h2>
<p>Methods introduced first take precedence over the latter ones: <br />
-<code class="highlighter-rouge">Programmatic Way > Java Options > Environment Variable > HTTP Endpoint</code></p>
+<code class="language-plaintext highlighter-rouge">Programmatic Way > Java Options > Environment Variable > HTTP Endpoint</code></p>
diff --git a/content/docs/best-practice-producer/index.html b/content/docs/best-practice-producer/index.html
index 9781bf2..9d9fc3a 100644
--- a/content/docs/best-practice-producer/index.html
+++ b/content/docs/best-practice-producer/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
diff --git a/content/docs/broadcast-example/index.html b/content/docs/broadcast-example/index.html
index b2ae2ad..708a2f9 100644
--- a/content/docs/broadcast-example/index.html
+++ b/content/docs/broadcast-example/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
diff --git a/content/docs/cli-admin-tool/index.html b/content/docs/cli-admin-tool/index.html
index b660501..01bc87f 100644
--- a/content/docs/cli-admin-tool/index.html
+++ b/content/docs/cli-admin-tool/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
@@ -489,9 +489,9 @@
<p>The Admin Tool is very user friendly. Here, for demonstration purpose, *nix environment is assumed.</p>
-<p>Change directory to ${PACKAGE}/bin, command <code class="highlighter-rouge">bash mqadmin</code>, you should see the following help menu.</p>
+<p>Change directory to ${PACKAGE}/bin, command <code class="language-plaintext highlighter-rouge">bash mqadmin</code>, you should see the following help menu.</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>The most commonly used mqadmin commands are:
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>The most commonly used mqadmin commands are:
updateTopic Update or create topic
deleteTopic Delete topic from broker and NameServer.
updateSubGroup Update or create subscription group
@@ -534,9 +534,9 @@
See 'mqadmin help <command>' for more information on a specific command.
</code></pre></div></div>
-<p>As you see, the most commonly used commands are listed with a brief description. To get detailed manual of each command, <code class="highlighter-rouge">bash mqadmin help <command></code>. For example, command <code class="highlighter-rouge">bash mqadmin help clusterList</code> will bring out the following help text:</p>
+<p>As you see, the most commonly used commands are listed with a brief description. To get detailed manual of each command, <code class="language-plaintext highlighter-rouge">bash mqadmin help <command></code>. For example, command <code class="language-plaintext highlighter-rouge">bash mqadmin help clusterList</code> will bring out the following help text:</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>usage: mqadmin clusterList [-h] [-i <arg>] [-m] [-n <arg>]
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>usage: mqadmin clusterList [-h] [-i <arg>] [-m] [-n <arg>]
-h,--help Print help
-i,--interval <arg> specify intervals numbers, it is in seconds
-m,--moreStats Print more stats
diff --git a/content/docs/cluster-deployment/index.html b/content/docs/cluster-deployment/index.html
index a181ce1..f02774e 100644
--- a/content/docs/cluster-deployment/index.html
+++ b/content/docs/cluster-deployment/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
@@ -524,8 +524,8 @@
<h1 id="deployment-example">Deployment Example</h1>
<p>For example, We want to have a cluster with 2 name servers, 2 broker sets with general purpose:
-for this example, we choose <code class="highlighter-rouge">2m-2s-sync</code>
-Assuming binary RocketMQ is at <code class="highlighter-rouge">/home/rocketmq/dist</code></p>
+for this example, we choose <code class="language-plaintext highlighter-rouge">2m-2s-sync</code>
+Assuming binary RocketMQ is at <code class="language-plaintext highlighter-rouge">/home/rocketmq/dist</code></p>
<ol>
<li>
@@ -534,22 +534,22 @@ Assuming binary RocketMQ is at <code class="highlighter-rouge">/home/rocketmq/di
<li>
<p>Start brokers</p>
- <p><code class="highlighter-rouge">cd /home/rocketmq/dist/bin</code></p>
+ <p><code class="language-plaintext highlighter-rouge">cd /home/rocketmq/dist/bin</code></p>
- <p><code class="highlighter-rouge">bash mqbroker -c ../conf/2m-2s-sync/broker-a.properties -n 192.168.0.2:9876,192.168.0.3:9876</code></p>
+ <p><code class="language-plaintext highlighter-rouge">bash mqbroker -c ../conf/2m-2s-sync/broker-a.properties -n 192.168.0.2:9876,192.168.0.3:9876</code></p>
- <p><code class="highlighter-rouge">bash mqbroker -c ../conf/2m-2s-sync/broker-a-s.properties -n 192.168.0.2:9876,192.168.0.3:9876</code></p>
+ <p><code class="language-plaintext highlighter-rouge">bash mqbroker -c ../conf/2m-2s-sync/broker-a-s.properties -n 192.168.0.2:9876,192.168.0.3:9876</code></p>
- <p><code class="highlighter-rouge">bash mqbroker -c ../conf/2m-2s-sync/broker-b.properties -n 192.168.0.2:9876,192.168.0.3:9876</code></p>
+ <p><code class="language-plaintext highlighter-rouge">bash mqbroker -c ../conf/2m-2s-sync/broker-b.properties -n 192.168.0.2:9876,192.168.0.3:9876</code></p>
- <p><code class="highlighter-rouge">bash mqbroker -c ../conf/2m-2s-sync/broker-b-s.properties -n 192.168.0.2:9876,192.168.0.3:9876</code></p>
+ <p><code class="language-plaintext highlighter-rouge">bash mqbroker -c ../conf/2m-2s-sync/broker-b-s.properties -n 192.168.0.2:9876,192.168.0.3:9876</code></p>
</li>
<li>
<p>Verify</p>
<p>Execute the following command to verify</p>
- <p><code class="highlighter-rouge">bash mqadmin clusterList</code></p>
+ <p><code class="language-plaintext highlighter-rouge">bash mqadmin clusterList</code></p>
</li>
</ol>
diff --git a/content/docs/code-guidelines/index.html b/content/docs/code-guidelines/index.html
index 8257fd2..fe498c3 100644
--- a/content/docs/code-guidelines/index.html
+++ b/content/docs/code-guidelines/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
diff --git a/content/docs/core-concept/index.html b/content/docs/core-concept/index.html
index 2b617ca..f9ccb41 100644
--- a/content/docs/core-concept/index.html
+++ b/content/docs/core-concept/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
diff --git a/content/docs/create-pull-request/index.html b/content/docs/create-pull-request/index.html
index f9d1b97..73cd2c3 100644
--- a/content/docs/create-pull-request/index.html
+++ b/content/docs/create-pull-request/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
@@ -477,38 +477,38 @@
</aside>
<h1 id="git-setup-for-contributors">Git setup for Contributors</h1>
-<p>First of all, fork github’s <code class="highlighter-rouge">apache/rocketmq</code> to your own account on github and clone it as follows,</p>
+<p>First of all, fork github’s <code class="language-plaintext highlighter-rouge">apache/rocketmq</code> to your own account on github and clone it as follows,</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git clone https://github.com/<your_github_name>/rocketmq.git
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git clone https://github.com/<your_github_name>/rocketmq.git
</code></pre></div></div>
-<p>Cloning this locally will set up <code class="highlighter-rouge">origin</code> to point to your remote fork on github as the default remote.
+<p>Cloning this locally will set up <code class="language-plaintext highlighter-rouge">origin</code> to point to your remote fork on github as the default remote.
Now you can create your pull requests.</p>
<p>You will need to update a local master sometimes (to merge to your development branches sometimes).
For this, you have to add remote for RocketMQ mirror as follows,</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git remote add upstream https://github.com/apache/rocketmq.git
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git remote add upstream https://github.com/apache/rocketmq.git
</code></pre></div></div>
-<p>and update your local master via <code class="highlighter-rouge">git fetch</code> followed by <code class="highlighter-rouge">git rebase</code>, for instance:
+<p>and update your local master via <code class="language-plaintext highlighter-rouge">git fetch</code> followed by <code class="language-plaintext highlighter-rouge">git rebase</code>, for instance:
git fetch upstream master
git rebase upstream/master</p>
<h1 id="git-setup-for-committers">Git setup for Committers</h1>
<p>In addition to contributors’ configurations, committers will have to attach the apache git repo:</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git remote add apache https://git-wip-us.apache.org/repos/asf/rocketmq.git
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git remote add apache https://git-wip-us.apache.org/repos/asf/rocketmq.git
</code></pre></div></div>
<p>To check your remote setup, issue</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git remote -v
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git remote -v
</code></pre></div></div>
<p>You should see something like this:</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>origin https://github.com/<your_github_name>/rocketmq.git (fetch)
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>origin https://github.com/<your_github_name>/rocketmq.git (fetch)
origin https://github.com/<your_github_name>/rocketmq.git (push)
upstream https://github.com/apache/rocketmq.git (fetch)
upstream https://github.com/apache/rocketmq.git (push)
@@ -518,14 +518,14 @@ apache https://git-wip-us.apache.org/repos/asf/rocketmq.git (push)
<p>Now if you want to experiment with a branch everything, by default, points to your github account because ‘origin’ is default. You can work as normal using only github until you are ready to merge with the apache remote. Some conventions will integrate with Apache JIRA ticket numbers.</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git checkout -b ROCKETMQ-xxxx #xxxx typically is a JIRA ticket number
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git checkout -b ROCKETMQ-xxxx #xxxx typically is a JIRA ticket number
</code></pre></div></div>
<p><em>To ensure the code quality of the master branch, all but minor changes should go through pull requests reviewed by peer committers.</em></p>
<h1 id="do-some-work-on-the-branch">Do some work on the branch</h1>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git commit -a -m "doing some work"
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git commit -a -m "doing some work"
git push origin ROCKETMQ-xxxx # notice pushing to **origin** not **apache**
</code></pre></div></div>
@@ -535,7 +535,7 @@ git push origin ROCKETMQ-xxxx # notice pushing to **origin** not **apache**
<p>Push your branch to Github:</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git checkout ROCKETMQ-xxxx
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git checkout ROCKETMQ-xxxx
git push origin ROCKETMQ-xxxx
</code></pre></div></div>
@@ -560,7 +560,7 @@ git push origin ROCKETMQ-xxxx
<p>For information about creating pull requests, please check <a href="https://help.github.com/articles/creating-a-pull-request/">GitHub PR docs</a>.</p>
-<p>Pull requests are made to <code class="highlighter-rouge">apache/rocketmq</code> repository on Github.
+<p>Pull requests are made to <code class="language-plaintext highlighter-rouge">apache/rocketmq</code> repository on Github.
In the Github UI you can pick the develop branch as target of the PR. <br />
You pull request will be reviewed and commented by committers, and issues can be discussed. When all reviewers are positive on the pull request, it will be merged.</p>
diff --git a/content/docs/documentation/index.html b/content/docs/documentation/index.html
index 1ab2897..396e847 100644
--- a/content/docs/documentation/index.html
+++ b/content/docs/documentation/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
@@ -488,7 +488,7 @@ commented fully – method purpose, return value, parameters and exceptions.</p>
<p>Below is an example:</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>/**
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>/**
* Send message in synchronous mode. This method returns only when the sending procedure totally completes.
* </p>
*
diff --git a/content/docs/faq/index.html b/content/docs/faq/index.html
index 8e77627..713ee51 100644
--- a/content/docs/faq/index.html
+++ b/content/docs/faq/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
@@ -522,7 +522,7 @@ The broadcaset consumption still ensures that a message is consumered at least o
<h3 id="3-how-to-set-the-number-of-consumer-threads">3. How to set the number of consumer threads?</h3>
<p>When you start Consumer, set a ConsumeThreadNums property, example is as follows:</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>consumer.setConsumeThreadMin(20);
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>consumer.setConsumeThreadMin(20);
consumer.setConsumeThreadMax(20);
</code></pre></div></div>
diff --git a/content/docs/filter-by-sql92-example/index.html b/content/docs/filter-by-sql92-example/index.html
index b7ca967..56ced65 100644
--- a/content/docs/filter-by-sql92-example/index.html
+++ b/content/docs/filter-by-sql92-example/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
@@ -508,10 +508,10 @@
<p>RocketMQ only defines some basic grammars to support this feature. You could also extend it easily.</p>
<ol>
- <li>Numeric comparison, like <code class="highlighter-rouge">></code>, <code class="highlighter-rouge">>=</code>, <code class="highlighter-rouge"><</code>, <code class="highlighter-rouge"><=</code>, <code class="highlighter-rouge">BETWEEN</code>, <code class="highlighter-rouge">=</code>;</li>
- <li>Character comparison, like <code class="highlighter-rouge">=</code>, <code class="highlighter-rouge"><></code>, <code class="highlighter-rouge">IN</code>;</li>
- <li><code class="highlighter-rouge">IS NULL</code> or <code class="highlighter-rouge">IS NOT NULL</code>;</li>
- <li>Logical <code class="highlighter-rouge">AND</code>, <code class="highlighter-rouge">OR</code>, <code class="highlighter-rouge">NOT</code>;</li>
+ <li>Numeric comparison, like <code class="language-plaintext highlighter-rouge">></code>, <code class="language-plaintext highlighter-rouge">>=</code>, <code class="language-plaintext highlighter-rouge"><</code>, <code class="language-plaintext highlighter-rouge"><=</code>, <code class="language-plaintext highlighter-rouge">BETWEEN</code>, <code class="language-plaintext highlighter-rouge">=</code>;</li>
+ <li>Character comparison, like <code class="language-plaintext highlighter-rouge">=</code>, <code class="language-plaintext highlighter-rouge"><></code>, <code class="language-plaintext highlighter-rouge">IN</code>;</li>
+ <li><code class="language-plaintext highlighter-rouge">IS NULL</code> or <code class="language-plaintext highlighter-rouge">IS NOT NULL</code>;</li>
+ <li>Logical <code class="language-plaintext highlighter-rouge">AND</code>, <code class="language-plaintext highlighter-rouge">OR</code>, <code class="language-plaintext highlighter-rouge">NOT</code>;</li>
</ol>
<p>Constant types are:</p>
@@ -519,19 +519,19 @@
<ol>
<li>Numeric, like 123, 3.1415;</li>
<li>Character, like ‘abc’, must be made with single quotes;</li>
- <li><code class="highlighter-rouge">NULL</code>, special constant;</li>
- <li>Boolean, <code class="highlighter-rouge">TRUE</code> or <code class="highlighter-rouge">FALSE</code>;</li>
+ <li><code class="language-plaintext highlighter-rouge">NULL</code>, special constant;</li>
+ <li>Boolean, <code class="language-plaintext highlighter-rouge">TRUE</code> or <code class="language-plaintext highlighter-rouge">FALSE</code>;</li>
</ol>
<h3 id="usage-constraints">Usage constraints</h3>
<p>Only push consumer could select messages by SQL92. The interface is:</p>
-<p><code class="highlighter-rouge">public void subscribe(final String topic, final MessageSelector messageSelector)</code></p>
+<p><code class="language-plaintext highlighter-rouge">public void subscribe(final String topic, final MessageSelector messageSelector)</code></p>
<h3 id="producer-example">Producer example</h3>
-<p>You can put properties in message through method <code class="highlighter-rouge">putUserProperty</code> when sending.</p>
+<p>You can put properties in message through method <code class="language-plaintext highlighter-rouge">putUserProperty</code> when sending.</p>
<div class="language-java highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nc">DefaultMQProducer</span> <span class="n">producer</span> <span class="o">=</span> <span class="k">new</span> <span class="nc">DefaultMQProducer</span><span class="o">(</span><span class="s">"please_rename_unique_group_name"</span><span class="o">);</span>
<span class="n">producer</span><span class="o">.</span><span class="na">start</span><span class="o">();</span>
@@ -550,7 +550,7 @@
<h3 id="consumer-example">Consumer example</h3>
-<p>Use <code class="highlighter-rouge">MessageSelector.bySql</code> to select messages through SQL92 when consuming.</p>
+<p>Use <code class="language-plaintext highlighter-rouge">MessageSelector.bySql</code> to select messages through SQL92 when consuming.</p>
<div class="language-java highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nc">DefaultMQPushConsumer</span> <span class="n">consumer</span> <span class="o">=</span> <span class="k">new</span> <span class="nc">DefaultMQPushConsumer</span><span class="o">(</span><span class="s">"please_rename_unique_group_name_4"</span><span class="o">);</span>
diff --git a/content/docs/how-to-contribute/index.html b/content/docs/how-to-contribute/index.html
index 5c675ce..9ad5d4f 100644
--- a/content/docs/how-to-contribute/index.html
+++ b/content/docs/how-to-contribute/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
diff --git a/content/docs/logappender-example/index.html b/content/docs/logappender-example/index.html
index f4c192c..bfec926 100644
--- a/content/docs/logappender-example/index.html
+++ b/content/docs/logappender-example/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
@@ -478,7 +478,7 @@
<p>When using log4j properties config file,config as below.</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>log4j.appender.mq=org.apache.rocketmq.logappender.log4j.RocketmqLog4jAppender
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>log4j.appender.mq=org.apache.rocketmq.logappender.log4j.RocketmqLog4jAppender
log4j.appender.mq.Tag=yourTag
log4j.appender.mq.Topic=yourLogTopic
log4j.appender.mq.ProducerGroup=yourLogGroup
@@ -489,7 +489,7 @@ log4j.appender.mq.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss} %-4r [%t] (%F
<p>When using log4j xml config file,config it as this and also add a async appender:</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code><appender name="mqAppender1" class="org.apache.rocketmq.logappender.log4j.RocketmqLog4jAppender">
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code><appender name="mqAppender1" class="org.apache.rocketmq.logappender.log4j.RocketmqLog4jAppender">
<param name="Tag" value="yourTag" />
<param name="Topic" value="yourLogTopic" />
<param name="ProducerGroup" value="yourLogGroup" />
@@ -509,7 +509,7 @@ log4j.appender.mq.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss} %-4r [%t] (%F
<h4 id="log4j2">log4j2</h4>
<p>When using log4j2,config as this.If you want noneblock,just config an asyncAppender for ref.</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code><RocketMQ name="rocketmqAppender" producerGroup="yourLogGroup" nameServerAddress="yourRocketmqNameserverAddress"
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code><RocketMQ name="rocketmqAppender" producerGroup="yourLogGroup" nameServerAddress="yourRocketmqNameserverAddress"
topic="yourLogTopic" tag="yourTag">
<PatternLayout pattern="%d [%p] hahahah %c %m%n"/>
</RocketMQ>
@@ -519,7 +519,7 @@ log4j.appender.mq.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss} %-4r [%t] (%F
<h4 id="logback">logback</h4>
<p>When using logback,an asyncAppender also needed.</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code><appender name="mqAppender1" class="org.apache.rocketmq.logappender.logback.RocketmqLogbackAppender">
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code><appender name="mqAppender1" class="org.apache.rocketmq.logappender.logback.RocketmqLogbackAppender">
<tag>yourTag</tag>
<topic>yourLogTopic</topic>
<producerGroup>yourLogGroup</producerGroup>
diff --git a/content/docs/motivation/index.html b/content/docs/motivation/index.html
index 42992c6..5b91246 100644
--- a/content/docs/motivation/index.html
+++ b/content/docs/motivation/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
diff --git a/content/docs/openmessaging-example/index.html b/content/docs/openmessaging-example/index.html
index 9f0ac3b..e44e47b 100644
--- a/content/docs/openmessaging-example/index.html
+++ b/content/docs/openmessaging-example/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
diff --git a/content/docs/order-example/index.html b/content/docs/order-example/index.html
index 74e88c7..f746aac 100644
--- a/content/docs/order-example/index.html
+++ b/content/docs/order-example/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
diff --git a/content/docs/pull-request/index.html b/content/docs/pull-request/index.html
index a8c3ef6..89d7860 100644
--- a/content/docs/pull-request/index.html
+++ b/content/docs/pull-request/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
@@ -479,29 +479,29 @@
</aside>
<h1 id="git-setup-for-contributors">Git setup for Contributors</h1>
-<p>First of all, fork github’s <code class="highlighter-rouge">apache/rocketmq</code> to your own account on github and clone it as follows,</p>
+<p>First of all, fork github’s <code class="language-plaintext highlighter-rouge">apache/rocketmq</code> to your own account on github and clone it as follows,</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git clone https://github.com/<your_github_name>/rocketmq.git
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git clone https://github.com/<your_github_name>/rocketmq.git
</code></pre></div></div>
-<p>Cloning this locally will set up <code class="highlighter-rouge">origin</code> to point to your remote fork on github as the default remote.
+<p>Cloning this locally will set up <code class="language-plaintext highlighter-rouge">origin</code> to point to your remote fork on github as the default remote.
Now you can create your pull requests.</p>
<p>You will need to update a local master sometimes (to merge to your development branches).
For this, you have to add remote for RocketMQ mirror as follows,</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git remote add apache https://github.com/apache/rocketmq.git
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git remote add apache https://github.com/apache/rocketmq.git
</code></pre></div></div>
-<p>and update your local master via <code class="highlighter-rouge">git fetch</code> followed by <code class="highlighter-rouge">git rebase</code>, for instance:</p>
+<p>and update your local master via <code class="language-plaintext highlighter-rouge">git fetch</code> followed by <code class="language-plaintext highlighter-rouge">git rebase</code>, for instance:</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git fetch apache master
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git fetch apache master
git rebase apache/master
</code></pre></div></div>
<h1 id="do-some-work-on-the-branch">Do some work on the branch</h1>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git commit -a -m "doing some work"
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git commit -a -m "doing some work"
git push origin ROCKETMQ-xxxx # notice pushing to **origin** not **apache**
</code></pre></div></div>
@@ -511,7 +511,7 @@ git push origin ROCKETMQ-xxxx # notice pushing to **origin** not **apache**
<p>Push your branch to Github:</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git checkout ROCKETMQ-xxxx
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git checkout ROCKETMQ-xxxx
git push origin ROCKETMQ-xxxx
</code></pre></div></div>
@@ -536,7 +536,7 @@ git push origin ROCKETMQ-xxxx
<p>For information about creating pull requests, please check <a href="https://help.github.com/articles/creating-a-pull-request/">GitHub PR docs</a>.</p>
-<p>Pull requests are made to <code class="highlighter-rouge">apache/rocketmq</code> repository on Github.
+<p>Pull requests are made to <code class="language-plaintext highlighter-rouge">apache/rocketmq</code> repository on Github.
In the Github UI you should pick the develop branch as target of the PR. <br />
You pull request will be reviewed and commented by committers, and issues can be discussed. When all reviewers are positive on the pull request, it will be merged.</p>
@@ -544,22 +544,22 @@ You pull request will be reviewed and commented by committers, and issues can be
<p>Each pull request should follow the <a href="https://github.com/apache/rocketmq/blob/master/.github/PULL_REQUEST_TEMPLATE.md">checklist</a> to help us incorporate your contribution quickly and easily.</p>
-<p>Remember use <code class="highlighter-rouge">- [x]</code> mark an item finished in the check list and there is a <a href="https://github.com/apache/rocketmq/pull/152">demo pull request</a> can be your reference.</p>
+<p>Remember use <code class="language-plaintext highlighter-rouge">- [x]</code> mark an item finished in the check list and there is a <a href="https://github.com/apache/rocketmq/pull/152">demo pull request</a> can be your reference.</p>
<h1 id="merging-a-pr-yours-or-contributors">Merging a PR (yours or contributors)</h1>
<p>Start with reading <a href="https://help.github.com/articles/checking-out-pull-requests-locally/">GitHub PR merging locally</a>. Remember that pull requests are equivalent to a remote github branch with potentially a multitude of commits. In this case it is recommended to squash remote commit history to have one commit per issue, rather than merging in a multitude of contributor’s commits. In order to do that, as well as to close the PR at the same time, it is recommended to use squas [...]
Merging pull requests are equivalent to a “pull” of a contributor’s branch:</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git checkout master # switch to local master branch
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git checkout master # switch to local master branch
git pull apache master # fast-forward to current remote HEAD
git pull --squash https://github.com/cuser/rocketmq.git ROCKETMQ-xxxx # merge to master
</code></pre></div></div>
-<p><code class="highlighter-rouge">--squash</code> ensures all PR history is squashed into single commit, and allows committer to use his/her own message. Please refer to git help for merge or pull for more information about <code class="highlighter-rouge">--squash</code> option. In this example we assume that the contributor’s Github handle is “cuser” and the PR branch name is “ROCKETMQ-xxxx”. Next, resolve all conflicts, or ask a contributor to rebase on top of master, if PR went out o [...]
+<p><code class="language-plaintext highlighter-rouge">--squash</code> ensures all PR history is squashed into single commit, and allows committer to use his/her own message. Please refer to git help for merge or pull for more information about <code class="language-plaintext highlighter-rouge">--squash</code> option. In this example we assume that the contributor’s Github handle is “cuser” and the PR branch name is “ROCKETMQ-xxxx”. Next, resolve all conflicts, or ask a contributor to reb [...]
<p>If you are ready to merge your own (committer’s) PR you only need to merge (not pull), since you have a local copy that you’ve been working on. This is the branch that you used to create the PR.</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git checkout master # switch to local master branch
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git checkout master # switch to local master branch
git pull apache master # fast-forward to current remote HEAD
git merge --squash ROCKETMQ-xxxx
</code></pre></div></div>
@@ -567,19 +567,19 @@ git merge --squash ROCKETMQ-xxxx
<p>Please run regular patch checks, build with tests enabled, and change CHANGELOG whenever needed.
If all requirements are met, you can commit the squashed request using:</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git commit --author="contributor_name <contributor_email>" -a -m "ROCKETMQ-XXXX description closes apache/rocketmq#ZZ"
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git commit --author="contributor_name <contributor_email>" -a -m "ROCKETMQ-XXXX description closes apache/rocketmq#ZZ"
</code></pre></div></div>
<p>ROCKETMQ-XXXX is all capitalized and ZZ is the pull request number on apache/rocketmq repository. Including “closes apache/rocketmq#ZZ” will close the PR automatically. More information can be found here <a href="https://help.github.com/articles/closing-issues-via-commit-messages/">GitHub PR closing docs.</a>.
Next, push to apache:</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git push apache master
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git push apache master
</code></pre></div></div>
<p>(this will require Apache handle credentials).
The PR, once pushed, will get mirrored to github. To update your github version push there too:</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git push origin master
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git push origin master
</code></pre></div></div>
<p>Note on squashing: Since squash discards remote branch history, repeated PRs from the same remote branch are difficult to be merged. The workflow implies that every new PR starts with a new rebased branch. This is more important for contributors to know, rather than for committers, because if new PR is not mergeable, github would warn at the start. Please watch for dupe PRs (based on same source branches).</p>
@@ -587,7 +587,7 @@ The PR, once pushed, will get mirrored to github. To update your github version
<h1 id="closing-a-pr-without-committing-for-committers">Closing a PR without committing (for committers)</h1>
<p>When we want to reject a PR (close without committing), we can just issue an empty commit on master’s HEAD without merging the PR:</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git commit --allow-empty -m "ROCKETMQ-XXXX closes apache/rocketmq#ZZ *Won't fix*"
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git commit --allow-empty -m "ROCKETMQ-XXXX closes apache/rocketmq#ZZ *Won't fix*"
git push apache master
</code></pre></div></div>
diff --git a/content/docs/quick-start/index.html b/content/docs/quick-start/index.html
index ec73d42..a9fc89a 100644
--- a/content/docs/quick-start/index.html
+++ b/content/docs/quick-start/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
@@ -538,7 +538,7 @@ and receive messages.</p>
<h2 id="send--receive-messages">Send & Receive Messages</h2>
-<p>Before sending/receiving messages, we need to tell clients the location of name servers. RocketMQ provides multiple ways to achieve this. For simplicity, we use environment variable <code class="highlighter-rouge">NAMESRV_ADDR</code></p>
+<p>Before sending/receiving messages, we need to tell clients the location of name servers. RocketMQ provides multiple ways to achieve this. For simplicity, we use environment variable <code class="language-plaintext highlighter-rouge">NAMESRV_ADDR</code></p>
<div class="language-shell highlighter-rouge"><div class="highlight"><pre class="highlight"><code> <span class="o">></span> <span class="nb">export </span><span class="nv">NAMESRV_ADDR</span><span class="o">=</span>localhost:9876
<span class="o">></span> sh bin/tools.sh org.apache.rocketmq.example.quickstart.Producer
@@ -563,7 +563,7 @@ Send shutdown request to mqnamesrv<span class="o">(</span>36664<span class="o">)
<p>The guide is working for windows 10 , please make sure you have powershell installed.</p>
-<p>Download latest binary release. and extract zip file into your local disk. Such as: <code class="highlighter-rouge">D:\rocketmq</code></p>
+<p>Download latest binary release. and extract zip file into your local disk. Such as: <code class="language-plaintext highlighter-rouge">D:\rocketmq</code></p>
<h2 id="add-environment-variables">Add Environment Variables</h2>
diff --git a/content/docs/release-manual.html b/content/docs/release-manual.html
index 40b46d9..d247f10 100644
--- a/content/docs/release-manual.html
+++ b/content/docs/release-manual.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
@@ -515,14 +515,14 @@
<ul>
<li>Create new pgp key. Please refer to <a href="http://www.apache.org/dev/openpgp.html">here</a> on how to use gpg key.</li>
- <li>Generate a new key via <code class="highlighter-rouge">gpg --full-generate-key</code>, and answer 4096 bits with no expiration time.</li>
- <li>Upload your key to a public key server by <code class="highlighter-rouge">gpg --keyserver pgpkeys.mit.edu --send-key <your key id></code>.</li>
- <li>Export your public key to a file by <code class="highlighter-rouge">gpg --armor --export <your key id> >> gpgapachekey.txt</code>.</li>
+ <li>Generate a new key via <code class="language-plaintext highlighter-rouge">gpg --full-generate-key</code>, and answer 4096 bits with no expiration time.</li>
+ <li>Upload your key to a public key server by <code class="language-plaintext highlighter-rouge">gpg --keyserver pgpkeys.mit.edu --send-key <your key id></code>.</li>
+ <li>Export your public key to a file by <code class="language-plaintext highlighter-rouge">gpg --armor --export <your key id> >> gpgapachekey.txt</code>.</li>
<li>Get the key signed by other committers(Optional).</li>
<li>Add the key to the RocketMQ <a href="https://dist.apache.org/repos/dist/dev/rocketmq/KEYS">KEYS file</a>.</li>
</ul>
-<p><strong>Tips:</strong> If you have more than one key in your gpg, set the code signing key to <code class="highlighter-rouge">~/.gnupg/gpg.conf</code> as default key is recommended.</p>
+<p><strong>Tips:</strong> If you have more than one key in your gpg, set the code signing key to <code class="language-plaintext highlighter-rouge">~/.gnupg/gpg.conf</code> as default key is recommended.</p>
<h4 id="13-prepare-your-maven-settings">1.3 Prepare Your Maven Settings</h4>
<p>Make sure your Maven settings.xml file contains the following:</p>
@@ -562,7 +562,7 @@
<p><strong>Tips:</strong> It is highly recommended to use <a href="http://maven.apache.org/guides/mini/guide-encryption.html">Maven’s password encryption capabilities</a> for your passwords.</p>
<h4 id="14-cleanup-issues">1.4 Cleanup Issues</h4>
-<p>Cleanup JIRA issues or Github Issues related to this release version, and check all the issues has been marked with right version in the <code class="highlighter-rouge">FixVersion</code> field.</p>
+<p>Cleanup JIRA issues or Github Issues related to this release version, and check all the issues has been marked with right version in the <code class="language-plaintext highlighter-rouge">FixVersion</code> field.</p>
<p>Also, remember to check the current version of MQVersion, which should be equal to this released version.</p>
@@ -573,7 +573,7 @@
<p>In this process, you need to use maven release plugin to release the artifact to maven repository. And also, copy them to the svn repository.</p>
<h4 id="21-check-the-mqversion">2.1 Check the MQVersion</h4>
-<p>Remember to check the current version of MQVersion again, which should be equal to this released version like <code class="highlighter-rouge">release-4.5.0</code>.</p>
+<p>Remember to check the current version of MQVersion again, which should be equal to this released version like <code class="language-plaintext highlighter-rouge">release-4.5.0</code>.</p>
<div class="language-java highlighter-rouge"><div class="highlight"><pre class="highlight"><code> <span class="kd">public</span> <span class="kd">static</span> <span class="kd">final</span> <span class="kt">int</span> <span class="no">CURRENT_VERSION</span> <span class="o">=</span> <span class="nc">Version</span><span class="o">.</span><span class="na">V4_5_0</span><span class="o">.</span><span class="na">ordinal</span><span class="o">();</span>
</code></pre></div></div>
<h4 id="22-release-to-the-maven-repository">2.2 Release to the maven repository</h4>
@@ -582,17 +582,17 @@
Perform the following to generate and stage the artifacts:</p>
<ol>
- <li><code class="highlighter-rouge">mvn clean release:clean</code></li>
- <li><code class="highlighter-rouge">mvn release:prepare -Psigned_release -Darguments="-DskipTests"</code>, answer the correct release version(use the default, the version in pom, just enter), SCM release tag(use the default, the branch name, just enter), and the new development version(increate the version by 1.0, if you release 4.2.0, then the next version should be 4.3.0).</li>
- <li><code class="highlighter-rouge">mvn -Psigned_release release:perform -Darguments="-DskipTests"</code>, generate the artifacts and push them to the <a href="https://repository.apache.org/#stagingRepositories">Nexus repo</a>. If you would like to perform a dry run first (without pushing the artifacts to the repo), add the arg -DdryRun=true.</li>
+ <li><code class="language-plaintext highlighter-rouge">mvn clean release:clean</code></li>
+ <li><code class="language-plaintext highlighter-rouge">mvn release:prepare -Psigned_release -Darguments="-DskipTests"</code>, answer the correct release version(use the default, the version in pom, just enter), SCM release tag(use the default, the branch name, just enter), and the new development version(increate the version by 1.0, if you release 4.2.0, then the next version should be 4.3.0).</li>
+ <li><code class="language-plaintext highlighter-rouge">mvn -Psigned_release release:perform -Darguments="-DskipTests"</code>, generate the artifacts and push them to the <a href="https://repository.apache.org/#stagingRepositories">Nexus repo</a>. If you would like to perform a dry run first (without pushing the artifacts to the repo), add the arg -DdryRun=true.</li>
</ol>
-<p>Now, the candidate release artifacts can be found in the <a href="https://repository.apache.org/#stagingRepositories">Nexus staging repo</a> and in the <code class="highlighter-rouge">target</code> folder of your local branch.</p>
+<p>Now, the candidate release artifacts can be found in the <a href="https://repository.apache.org/#stagingRepositories">Nexus staging repo</a> and in the <code class="language-plaintext highlighter-rouge">target</code> folder of your local branch.</p>
-<p><strong>Tips:</strong> If you are performing a source-only release, please remove all artifacts from the staging repo besides the .zip file containing the source and the javadocs jar file. In the Nexus GUI, you can right click on each artifact to be deleted and then select <code class="highlighter-rouge">Delete</code>.</p>
+<p><strong>Tips:</strong> If you are performing a source-only release, please remove all artifacts from the staging repo besides the .zip file containing the source and the javadocs jar file. In the Nexus GUI, you can right click on each artifact to be deleted and then select <code class="language-plaintext highlighter-rouge">Delete</code>.</p>
<h4 id="23-checkout-release-branch">2.3 Checkout release branch</h4>
-<p>Checkout a new branch from the target branch(master or develop) according to the release tag with its name equal to the release version, like <code class="highlighter-rouge">release-4.5.0</code>.</p>
+<p>Checkout a new branch from the target branch(master or develop) according to the release tag with its name equal to the release version, like <code class="language-plaintext highlighter-rouge">release-4.5.0</code>.</p>
<h4 id="24-rollback-and-retry">2.4 Rollback and Retry</h4>
<p>If the staging process encounter problem, you may need to rollback:
@@ -604,8 +604,8 @@ Be aware of the os version, for some dependency is os sensitive, such as netty t
<ul>
<li>Make sure that your are in the candidate release branch.</li>
- <li>Make sure that all the unit tests can pass via <code class="highlighter-rouge">mvn clean install</code>.</li>
- <li>Make sure that all the integration tests can pass via <code class="highlighter-rouge">mvn clean test -Pit-test</code>.</li>
+ <li>Make sure that all the unit tests can pass via <code class="language-plaintext highlighter-rouge">mvn clean install</code>.</li>
+ <li>Make sure that all the integration tests can pass via <code class="language-plaintext highlighter-rouge">mvn clean test -Pit-test</code>.</li>
</ul>
<p>After the successful building, remember to sign the artifact(PGP and SHA512 signatures are required), and copy them to the svn repository, you could refer to <a href="https://dist.apache.org/repos/dist/release/rocketmq/">svn repository</a> .</p>
@@ -668,7 +668,7 @@ Be aware of the os version, for some dependency is os sensitive, such as netty t
</code></pre></div></div>
<h2 id="5-release-the-staging-artifacts">5. Release the Staging Artifacts</h2>
-<p>If the release candidate passes the validation checklist, close the staging repository in Nexus by selecting the staging repository <code class="highlighter-rouge">orgapacherocketmq-XXX</code> and clicking on the <code class="highlighter-rouge">Close</code> icon.</p>
+<p>If the release candidate passes the validation checklist, close the staging repository in Nexus by selecting the staging repository <code class="language-plaintext highlighter-rouge">orgapacherocketmq-XXX</code> and clicking on the <code class="language-plaintext highlighter-rouge">Close</code> icon.</p>
<p>Nexus will now run through a series of checksum and signature validations.</p>
@@ -752,7 +752,7 @@ The Apache RocketMQ Team</p>
<p>Once the Apache RocketMQ PPMC votes pass, publish the release artifacts to the Nexus Maven repository and to the Apache release repository.</p>
<ol>
- <li>Publish the Maven Artifacts, release the Maven artifacts in Nexus by selecting the staging repository <strong>orgapacherocketmq-XXX</strong> and clicking on the <code class="highlighter-rouge">Release</code> icon.</li>
+ <li>Publish the Maven Artifacts, release the Maven artifacts in Nexus by selecting the staging repository <strong>orgapacherocketmq-XXX</strong> and clicking on the <code class="language-plaintext highlighter-rouge">Release</code> icon.</li>
<li>Publish the Artifacts to the Apache Release Repository, use svn copy candidate release artifacts to https://dist.apache.org/repos/dist/release/rocketmq/${release-version}</li>
</ol>
diff --git a/content/docs/rmq-arc/index.html b/content/docs/rmq-arc/index.html
index 8b660fb..49a3919 100644
--- a/content/docs/rmq-arc/index.html
+++ b/content/docs/rmq-arc/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
@@ -509,9 +509,9 @@ RocketMQ’s website provides a simple quick-start guide to interested users.</p
<p>There are four methods to feed NameServer address list to clients:</p>
<ul>
- <li>Programmatic Way, like <code class="highlighter-rouge">producer.setNamesrvAddr("ip:port")</code>.</li>
- <li>Java Options, use <code class="highlighter-rouge">rocketmq.namesrv.addr</code>.</li>
- <li>Environment Variable, use <code class="highlighter-rouge">NAMESRV_ADDR</code>.</li>
+ <li>Programmatic Way, like <code class="language-plaintext highlighter-rouge">producer.setNamesrvAddr("ip:port")</code>.</li>
+ <li>Java Options, use <code class="language-plaintext highlighter-rouge">rocketmq.namesrv.addr</code>.</li>
+ <li>Environment Variable, use <code class="language-plaintext highlighter-rouge">NAMESRV_ADDR</code>.</li>
<li>HTTP Endpoint.</li>
</ul>
diff --git a/content/docs/rmq-deployment/index.html b/content/docs/rmq-deployment/index.html
index 509d0b2..6a03132 100644
--- a/content/docs/rmq-deployment/index.html
+++ b/content/docs/rmq-deployment/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
diff --git a/content/docs/roadmap/index.html b/content/docs/roadmap/index.html
index 57ad051..e58ddca 100644
--- a/content/docs/roadmap/index.html
+++ b/content/docs/roadmap/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
@@ -490,7 +490,7 @@
</aside>
<h3 id="message-filtering">Message Filtering</h3>
-<p>So far, RocketMQ only supports message filtering feature by <code class="highlighter-rouge">TAG</code>, but one message can only own one tag, which is too limited to meet complex business requirements.</p>
+<p>So far, RocketMQ only supports message filtering feature by <code class="language-plaintext highlighter-rouge">TAG</code>, but one message can only own one tag, which is too limited to meet complex business requirements.</p>
<p>So, we want to define and implement a reasonable filter language based on a subset of the SQL 92 expression syntax to support customized message filtering. <a href="https://issues.apache.org/jira/browse/ROCKETMQ-121">JIRA</a></p>
diff --git a/content/docs/schedule-example/index.html b/content/docs/schedule-example/index.html
index 3fcfd69..056722f 100644
--- a/content/docs/schedule-example/index.html
+++ b/content/docs/schedule-example/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
diff --git a/content/docs/simple-example/index.html b/content/docs/simple-example/index.html
index d3c04a5..8155fa2 100644
--- a/content/docs/simple-example/index.html
+++ b/content/docs/simple-example/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
diff --git a/content/docs/system-config/index.html b/content/docs/system-config/index.html
index 370d2d9..6ccc047 100644
--- a/content/docs/system-config/index.html
+++ b/content/docs/system-config/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
@@ -478,41 +478,41 @@
<p>The latest released version of JDK 1.8 is recommended, with server compiler and a 8g heap. Set the same Xms and Xmx value to prevent the JVM from resizing the heap for better performance. A simple JVM configurations looks like this:</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>-server -Xms8g -Xmx8g -Xmn4g
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>-server -Xms8g -Xmx8g -Xmn4g
</code></pre></div></div>
<p>If you don’t care about the boot time of RocketMQ broker, pre-touch the Java heap to make sure that every page will be allocated during JVM initialization is a better choice. Those who don’t care about the boot time can enable it:</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>-XX:+AlwaysPreTouch
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>-XX:+AlwaysPreTouch
</code></pre></div></div>
<p>Disable biased locking may reduce JVM pauses:</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>-XX:-UseBiasedLocking
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>-XX:-UseBiasedLocking
</code></pre></div></div>
<p>As for garbage collection, G1 collector with JDK 1.8 is recommended:</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>-XX:+UseG1GC -XX:G1HeapRegionSize=16m -XX:G1ReservePercent=25 -XX:InitiatingHeapOccupancyPercent=30
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>-XX:+UseG1GC -XX:G1HeapRegionSize=16m -XX:G1ReservePercent=25 -XX:InitiatingHeapOccupancyPercent=30
</code></pre></div></div>
<p>These GC options looks a little aggressive, but it’s proved to have good performance in our production environment.</p>
-<p>Don’t set a too small value for <code class="highlighter-rouge">-XX:MaxGCPauseMillis</code>, otherwise JVM will use a small young generation to achieve this goal which will cause very frequent minor GC.</p>
+<p>Don’t set a too small value for <code class="language-plaintext highlighter-rouge">-XX:MaxGCPauseMillis</code>, otherwise JVM will use a small young generation to achieve this goal which will cause very frequent minor GC.</p>
<p>And use rolling GC log file is recommended:</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>-XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=30m
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>-XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=30m
</code></pre></div></div>
<p>If write GC file will increase latency of broker, consider redirect GC log file to a memory file system:</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>-Xloggc:/dev/shm/mq_gc_%p.log
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>-Xloggc:/dev/shm/mq_gc_%p.log
</code></pre></div></div>
<h1 id="linux-kernel-parameters">Linux Kernel Parameters</h1>
-<p>There is a <code class="highlighter-rouge">os.sh</code> script that lists a lot of kernel parameters in folder <code class="highlighter-rouge">bin</code> which can be used for production use with minor changes. Below parameters need attention, and more details please refer to documentation for /proc/sys/vm/*[1].</p>
+<p>There is a <code class="language-plaintext highlighter-rouge">os.sh</code> script that lists a lot of kernel parameters in folder <code class="language-plaintext highlighter-rouge">bin</code> which can be used for production use with minor changes. Below parameters need attention, and more details please refer to documentation for /proc/sys/vm/*[1].</p>
<p><strong>vm.extra_free_kbytes</strong>, tells the VM to keep extra free memory between the threshold where background reclaim (kswapd) kicks in, and the threshold where direct reclaim (by allocating processes) kicks in. RocketMQ uses this parameter to avoid high latency in memory allocation.</p>
diff --git a/content/docs/transaction-example/index.html b/content/docs/transaction-example/index.html
index f113bad..f0640e4 100644
--- a/content/docs/transaction-example/index.html
+++ b/content/docs/transaction-example/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
diff --git a/content/dowloading/releases/index.html b/content/dowloading/releases/index.html
index 5e347d2..05c2340 100644
--- a/content/dowloading/releases/index.html
+++ b/content/dowloading/releases/index.html
@@ -57,7 +57,7 @@
<meta property="og:type" content="article">
- <meta property="article:published_time" content="2021-08-09T15:32:06+08:00">
+ <meta property="article:published_time" content="2021-08-11T17:46:15+08:00">
diff --git a/content/feed.xml b/content/feed.xml
index bd7d465..f4002cf 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.8.6">Jekyll</generator><link href="/feed.xml" rel="self" type="application/atom+xml" /><link href="/" rel="alternate" type="text/html" /><updated>2021-08-09T15:32:06+08:00</updated><id>/feed.xml</id><title type="html">Apache RocketMQ</title><subtitle>The homepage of RocketMQ.</subtitle><author><name>{"name"=>nil, "avatar"=>"/ass [...]
+<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.9.1">Jekyll</generator><link href="/feed.xml" rel="self" type="application/atom+xml" /><link href="/" rel="alternate" type="text/html" /><updated>2021-08-11T17:46:15+08:00</updated><id>/feed.xml</id><title type="html">Apache RocketMQ</title><subtitle>The homepage of RocketMQ.</subtitle><author><name>{"name"=>nil, "avatar"=>"/ass [...]
<h2> Download the 4.9.1 release</h2>
@@ -113,7 +113,7 @@
</li>
<li>[<a href="https://github.com/apache/rocketmq/issues/2990">ISSUE-2990</a>] - Add message tracing switch in sendMessage command of mqadmin, and add document.
</li>
-</ul></content><author><name>{"name"=>nil, "avatar"=>"/assets/images/rmq-logo.png", "bio"=>"An open source distributed messaging and streaming data platform.", "location"=>"Hangzhou, China", "email"=>"dev@rocketmq.apache.org", "uri"=>"http://rocketmq.apache.org", "bitbucket"=>nil, "codepen"=>nil, "dribbble"=>nil, &quo [...]
+</ul></content><author><name>{"name"=>nil, "avatar"=>"/assets/images/rmq-logo.png", "bio"=>"An open source distributed messaging and streaming data platform.", "location"=>"Hangzhou, China", "email"=>"dev@rocketmq.apache.org", "uri"=>"http://rocketmq.apache.org", "bitbucket"=>nil, "codepen"=>nil, "dribbble"=>nil, &quo [...]
<h2> Download the 4.9.0 release</h2>
@@ -198,7 +198,7 @@
</li>
<li>[<a href="https://github.com/apache/rocketmq/issues/2849">ISSUE-2849</a>] - maven checkstyle failed.
</li>
-</ul></content><author><name>{"name"=>nil, "avatar"=>"/assets/images/rmq-logo.png", "bio"=>"An open source distributed messaging and streaming data platform.", "location"=>"Hangzhou, China", "email"=>"dev@rocketmq.apache.org", "uri"=>"http://rocketmq.apache.org", "bitbucket"=>nil, "codepen"=>nil, "dribbble"=>nil, &quo [...]
+</ul></content><author><name>{"name"=>nil, "avatar"=>"/assets/images/rmq-logo.png", "bio"=>"An open source distributed messaging and streaming data platform.", "location"=>"Hangzhou, China", "email"=>"dev@rocketmq.apache.org", "uri"=>"http://rocketmq.apache.org", "bitbucket"=>nil, "codepen"=>nil, "dribbble"=>nil, &quo [...]
<h2> Download the 2.1.0 release</h2>
@@ -220,7 +220,7 @@
</li>
<li>[<a href="https://github.com/apache/rocketmq-client-go/releases/tag/v2.1.0-rc1">v2.1.0-rc1</a>] - Improvements in rocketmq client go 2.1.0 rc1.
</li>
-</ul></content><author><name>{"name"=>nil, "avatar"=>"/assets/images/rmq-logo.png", "bio"=>"An open source distributed messaging and streaming data platform.", "location"=>"Hangzhou, China", "email"=>"dev@rocketmq.apache.org", "uri"=>"http://rocketmq.apache.org", "bitbucket"=>nil, "codepen"=>nil, "dribbble"=>nil, &quo [...]
+</ul></content><author><name>{"name"=>nil, "avatar"=>"/assets/images/rmq-logo.png", "bio"=>"An open source distributed messaging and streaming data platform.", "location"=>"Hangzhou, China", "email"=>"dev@rocketmq.apache.org", "uri"=>"http://rocketmq.apache.org", "bitbucket"=>nil, "codepen"=>nil, "dribbble"=>nil, &quo [...]
<h2> Download the 2.2.0 release</h2>
@@ -260,7 +260,7 @@
</li>
<li>[<a href="https://github.com/apache/rocketmq-spring/issues/304">ISSUE #304</a>] - Fix the correspondence between enumerations and numbers.
</li>
-</ul></content><author><name>{"name"=>nil, "avatar"=>"/assets/images/rmq-logo.png", "bio"=>"An open source distributed messaging and streaming data platform.", "location"=>"Hangzhou, China", "email"=>"dev@rocketmq.apache.org", "uri"=>"http://rocketmq.apache.org", "bitbucket"=>nil, "codepen"=>nil, "dribbble"=>nil, &quo [...]
+</ul></content><author><name>{"name"=>nil, "avatar"=>"/assets/images/rmq-logo.png", "bio"=>"An open source distributed messaging and streaming data platform.", "location"=>"Hangzhou, China", "email"=>"dev@rocketmq.apache.org", "uri"=>"http://rocketmq.apache.org", "bitbucket"=>nil, "codepen"=>nil, "dribbble"=>nil, &quo [...]
<h2> Download the 4.8.0 release</h2>
@@ -391,7 +391,7 @@
</li>
<li>[<a href="https://github.com/apache/rocketmq/issues/2459">ISSUE-2459</a>] - Fix the error in best practice document.
</li>
-</ul></content><author><name>{"name"=>nil, "avatar"=>"/assets/images/rmq-logo.png", "bio"=>"An open source distributed messaging and streaming data platform.", "location"=>"Hangzhou, China", "email"=>"dev@rocketmq.apache.org", "uri"=>"http://rocketmq.apache.org", "bitbucket"=>nil, "codepen"=>nil, "dribbble"=>nil, &quo [...]
+</ul></content><author><name>{"name"=>nil, "avatar"=>"/assets/images/rmq-logo.png", "bio"=>"An open source distributed messaging and streaming data platform.", "location"=>"Hangzhou, China", "email"=>"dev@rocketmq.apache.org", "uri"=>"http://rocketmq.apache.org", "bitbucket"=>nil, "codepen"=>nil, "dribbble"=>nil, &quo [...]
<h2> Download the 2.1.1 release</h2>
@@ -419,7 +419,7 @@
</li>
<li>[<a href="https://github.com/apache/rocketmq-spring/pull/244">ISSUE #242</a>] - SyncSend batchMessage method without timeout param.
</li>
-</ul></content><author><name>{"name"=>nil, "avatar"=>"/assets/images/rmq-logo.png", "bio"=>"An open source distributed messaging and streaming data platform.", "location"=>"Hangzhou, China", "email"=>"dev@rocketmq.apache.org", "uri"=>"http://rocketmq.apache.org", "bitbucket"=>nil, "codepen"=>nil, "dribbble"=>nil, &quo [...]
+</ul></content><author><name>{"name"=>nil, "avatar"=>"/assets/images/rmq-logo.png", "bio"=>"An open source distributed messaging and streaming data platform.", "location"=>"Hangzhou, China", "email"=>"dev@rocketmq.apache.org", "uri"=>"http://rocketmq.apache.org", "bitbucket"=>nil, "codepen"=>nil, "dribbble"=>nil, &quo [...]
<h2> Download the 4.7.1 release</h2>
@@ -532,7 +532,7 @@
</li>
<li>[<a href="https://github.com/apache/rocketmq/issues/1505">ISSUE-1505</a>] - Fix document error about batch sample.
</li>
-</ul></content><author><name>{"name"=>nil, "avatar"=>"/assets/images/rmq-logo.png", "bio"=>"An open source distributed messaging and streaming data platform.", "location"=>"Hangzhou, China", "email"=>"dev@rocketmq.apache.org", "uri"=>"http://rocketmq.apache.org", "bitbucket"=>nil, "codepen"=>nil, "dribbble"=>nil, &quo [...]
+</ul></content><author><name>{"name"=>nil, "avatar"=>"/assets/images/rmq-logo.png", "bio"=>"An open source distributed messaging and streaming data platform.", "location"=>"Hangzhou, China", "email"=>"dev@rocketmq.apache.org", "uri"=>"http://rocketmq.apache.org", "bitbucket"=>nil, "codepen"=>nil, "dribbble"=>nil, &quo [...]
<h2> Download the 2.2.0 release</h2>
@@ -555,7 +555,7 @@
</li>
<li>[<a href="https://github.com/apache/rocketmq-client-cpp/pull/286">ISSUE-286</a>] - Add null pointer check before push consumer shutdown.
</li>
-</ul></content><author><name>{"name"=>nil, "avatar"=>"/assets/images/rmq-logo.png", "bio"=>"An open source distributed messaging and streaming data platform.", "location"=>"Hangzhou, China", "email"=>"dev@rocketmq.apache.org", "uri"=>"http://rocketmq.apache.org", "bitbucket"=>nil, "codepen"=>nil, "dribbble"=>nil, &quo [...]
+</ul></content><author><name>{"name"=>nil, "avatar"=>"/assets/images/rmq-logo.png", "bio"=>"An open source distributed messaging and streaming data platform.", "location"=>"Hangzhou, China", "email"=>"dev@rocketmq.apache.org", "uri"=>"http://rocketmq.apache.org", "bitbucket"=>nil, "codepen"=>nil, "dribbble"=>nil, &quo [...]
<h2> Download the 2.0.0 release</h2>
@@ -591,7 +591,7 @@
</li>
<li>[<a href="https://github.com/apache/rocketmq-client-go/pull/462">ISSUE-462</a>] - Fix the trace message was send failed.
</li>
-</ul></content><author><name>{"name"=>nil, "avatar"=>"/assets/images/rmq-logo.png", "bio"=>"An open source distributed messaging and streaming data platform.", "location"=>"Hangzhou, China", "email"=>"dev@rocketmq.apache.org", "uri"=>"http://rocketmq.apache.org", "bitbucket"=>nil, "codepen"=>nil, "dribbble"=>nil, &quo [...]
+</ul></content><author><name>{"name"=>nil, "avatar"=>"/assets/images/rmq-logo.png", "bio"=>"An open source distributed messaging and streaming data platform.", "location"=>"Hangzhou, China", "email"=>"dev@rocketmq.apache.org", "uri"=>"http://rocketmq.apache.org", "bitbucket"=>nil, "codepen"=>nil, "dribbble"=>nil, &quo [...]
<h2> Download the 2.1.0 release</h2>
@@ -643,4 +643,4 @@
<li>[<a href="https://github.com/apache/rocketmq-client-cpp/pull/241">ISSUE-241</a>] - Fix heap-buffer-overflow risk issues.
</li>
-</ul></content><author><name>{"name"=>nil, "avatar"=>"/assets/images/rmq-logo.png", "bio"=>"An open source distributed messaging and streaming data platform.", "location"=>"Hangzhou, China", "email"=>"dev@rocketmq.apache.org", "uri"=>"http://rocketmq.apache.org", "bitbucket"=>nil, "codepen"=>nil, "dribbble"=>nil, &quo [...]
\ No newline at end of file
+</ul></content><author><name>{"name"=>nil, "avatar"=>"/assets/images/rmq-logo.png", "bio"=>"An open source distributed messaging and streaming data platform.", "location"=>"Hangzhou, China", "email"=>"dev@rocketmq.apache.org", "uri"=>"http://rocketmq.apache.org", "bitbucket"=>nil, "codepen"=>nil, "dribbble"=>nil, &quo [...]
\ No newline at end of file
diff --git a/content/maven/mastering-component-compatible-dependency/index.html b/content/maven/mastering-component-compatible-dependency/index.html
index 4ff1758..bdc196b 100644
--- a/content/maven/mastering-component-compatible-dependency/index.html
+++ b/content/maven/mastering-component-compatible-dependency/index.html
@@ -513,7 +513,7 @@ have a class named StaticLoggerBinder and implementing SLF4J spi LoggerFactoryBi
<span class="o"></</span><span class="n">plugin</span><span class="o">></span>
</code></pre></div></div>
-<p>then,run <code class="highlighter-rouge">mvn clirr:check</code>,output may be like this:</p>
+<p>then,run <code class="language-plaintext highlighter-rouge">mvn clirr:check</code>,output may be like this:</p>
<div class="language-java highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="o">[</span><span class="no">INFO</span><span class="o">]</span> <span class="o">---</span> <span class="n">clirr</span><span class="o">-</span><span class="n">maven</span><span class="o">-</span><span class="nl">plugin:</span><span class="mf">2.6</span><span class="o">.</span><span class="mi">1</span><span class="o">:</span><span class="n">check</span> <span class="o">(</span><sp [...]
<span class="o">[</span><span class="no">INFO</span><span class="o">]</span> <span class="n">artifact</span> <span class="n">com</span><span class="o">.</span><span class="na">alibaba</span><span class="o">.</span><span class="na">intl</span><span class="o">.</span><span class="na">base</span><span class="o">.</span><span class="na">cmq</span><span class="o">:</span><span class="n">cmq</span><span class="o">.</span><span class="na">common</span><span class="o">:</span> <span class="n">ch [...]
diff --git a/content/rocketmq/filter-messages-by-sql92-in-rocketmq/index.html b/content/rocketmq/filter-messages-by-sql92-in-rocketmq/index.html
index 5784467..9fb3e20 100644
--- a/content/rocketmq/filter-messages-by-sql92-in-rocketmq/index.html
+++ b/content/rocketmq/filter-messages-by-sql92-in-rocketmq/index.html
@@ -309,7 +309,7 @@
<section class="page__content" itemprop="text">
- <p>So far, RocketMQ only support message filtering feature by <code class="highlighter-rouge">TAG</code>, but one message only can own one tag, this is too limited to meet complex business requirements.</p>
+ <p>So far, RocketMQ only support message filtering feature by <code class="language-plaintext highlighter-rouge">TAG</code>, but one message only can own one tag, this is too limited to meet complex business requirements.</p>
<p>So, we want to define and implement a reasonable filter language based on a subset of the SQL 92 expression syntax to support customized message filtering.</p>
@@ -320,10 +320,10 @@
<p>As I know, ActiveMQ already impllement this functionality based on JavaCC, it’s simple and exntensible.So I just extract it and integrate into RocketMQ, only some grammars:</p>
<ol>
- <li>Numeric comparison, like <code class="highlighter-rouge">></code>, <code class="highlighter-rouge">>=</code>, <code class="highlighter-rouge"><</code>, <code class="highlighter-rouge"><=</code>, <code class="highlighter-rouge">BETWEEN</code>, <code class="highlighter-rouge">=</code>;</li>
- <li>Character comparison, like <code class="highlighter-rouge">=</code>, <code class="highlighter-rouge"><></code>, <code class="highlighter-rouge">IN</code>;</li>
- <li><code class="highlighter-rouge">IS NULL</code> or <code class="highlighter-rouge">IS NOT NULL</code>;</li>
- <li>Logical <code class="highlighter-rouge">AND</code>, logical <code class="highlighter-rouge">OR</code>, logical <code class="highlighter-rouge">NOT</code>;</li>
+ <li>Numeric comparison, like <code class="language-plaintext highlighter-rouge">></code>, <code class="language-plaintext highlighter-rouge">>=</code>, <code class="language-plaintext highlighter-rouge"><</code>, <code class="language-plaintext highlighter-rouge"><=</code>, <code class="language-plaintext highlighter-rouge">BETWEEN</code>, <code class="language-plaintext highlighter-rouge">=</code>;</li>
+ <li>Character comparison, like <code class="language-plaintext highlighter-rouge">=</code>, <code class="language-plaintext highlighter-rouge"><></code>, <code class="language-plaintext highlighter-rouge">IN</code>;</li>
+ <li><code class="language-plaintext highlighter-rouge">IS NULL</code> or <code class="language-plaintext highlighter-rouge">IS NOT NULL</code>;</li>
+ <li>Logical <code class="language-plaintext highlighter-rouge">AND</code>, logical <code class="language-plaintext highlighter-rouge">OR</code>, logical <code class="language-plaintext highlighter-rouge">NOT</code>;</li>
</ol>
<p>Constant type are:</p>
@@ -331,8 +331,8 @@
<ol>
<li>Numeric, like 123, 3.1415;</li>
<li>Character, like ‘abc’, must be maked with single quotes;</li>
- <li><code class="highlighter-rouge">NULL</code>, special constant;</li>
- <li>Boolean, <code class="highlighter-rouge">TRUE</code> or <code class="highlighter-rouge">FALSE</code>;</li>
+ <li><code class="language-plaintext highlighter-rouge">NULL</code>, special constant;</li>
+ <li>Boolean, <code class="language-plaintext highlighter-rouge">TRUE</code> or <code class="language-plaintext highlighter-rouge">FALSE</code>;</li>
</ol>
<h3 id="design">Design</h3>
@@ -343,8 +343,8 @@
<p><img src="/assets/images/blog/filter_structure_apach.png" alt="screenshot" /></p>
<ol>
- <li>Broker collects the expression of consumer through heartbeat request, and saved in <code class="highlighter-rouge">ConsumerFilterManager</code>.</li>
- <li>When consumer pulls messages, broker will construct a <code class="highlighter-rouge">MessageFilter</code>(an interface) with compiled expression and subscription data to select matched messages in <code class="highlighter-rouge">CommitLog</code>.</li>
+ <li>Broker collects the expression of consumer through heartbeat request, and saved in <code class="language-plaintext highlighter-rouge">ConsumerFilterManager</code>.</li>
+ <li>When consumer pulls messages, broker will construct a <code class="language-plaintext highlighter-rouge">MessageFilter</code>(an interface) with compiled expression and subscription data to select matched messages in <code class="language-plaintext highlighter-rouge">CommitLog</code>.</li>
</ol>
<p>The main logic is simple.</p>
@@ -355,7 +355,7 @@
<p>The implementation of SQL92 language is placed in this module which have dependency on common module.</p>
-<p>Broker compile or evaluate expression through the interface of <code class="highlighter-rouge">FilterSpi</code> contained in <code class="highlighter-rouge">FilterFactory</code> that manage all <code class="highlighter-rouge">FilterSpi</code> and also support new one to register.</p>
+<p>Broker compile or evaluate expression through the interface of <code class="language-plaintext highlighter-rouge">FilterSpi</code> contained in <code class="language-plaintext highlighter-rouge">FilterFactory</code> that manage all <code class="language-plaintext highlighter-rouge">FilterSpi</code> and also support new one to register.</p>
<ul>
<li>How to manage consumer’s expression data</li>
@@ -363,15 +363,15 @@
<p>Different from tag filtering, expression of SQL92 should be compiled first to check whether is leagal and then use the complied expression to compute. This procedure is designed to take place at broker.</p>
-<p><code class="highlighter-rouge">ConsumerManager</code> manage the suscriptions of push consumer, and <code class="highlighter-rouge">ConsumerFilterManager</code> manage the expression info of push consumer who wish to filter message by special language, the info includes data version, expression, compiled expression, alive time and etc.</p>
+<p><code class="language-plaintext highlighter-rouge">ConsumerManager</code> manage the suscriptions of push consumer, and <code class="language-plaintext highlighter-rouge">ConsumerFilterManager</code> manage the expression info of push consumer who wish to filter message by special language, the info includes data version, expression, compiled expression, alive time and etc.</p>
<ul>
<li>How to filter message by expression</li>
</ul>
-<p>I redesign the interface <code class="highlighter-rouge">getMessage</code> of <code class="highlighter-rouge">MessageStore</code> by replace the last parameter <code class="highlighter-rouge">SubscriptionData</code> to <code class="highlighter-rouge">MessageFilter</code> that is also refactored. The purpose is to make module <code class="highlighter-rouge">rocketmq-store</code> has no relation with protocol.</p>
+<p>I redesign the interface <code class="language-plaintext highlighter-rouge">getMessage</code> of <code class="language-plaintext highlighter-rouge">MessageStore</code> by replace the last parameter <code class="language-plaintext highlighter-rouge">SubscriptionData</code> to <code class="language-plaintext highlighter-rouge">MessageFilter</code> that is also refactored. The purpose is to make module <code class="language-plaintext highlighter-rouge">rocketmq-store</code> has no relati [...]
-<p>When get message, the implementation <code class="highlighter-rouge">ExpressionMessageFilter</code> would check whether the message is matched by <code class="highlighter-rouge">BitsArray</code> which will be refered later or evaluation, just as the mechanism of tag filtering.</p>
+<p>When get message, the implementation <code class="language-plaintext highlighter-rouge">ExpressionMessageFilter</code> would check whether the message is matched by <code class="language-plaintext highlighter-rouge">BitsArray</code> which will be refered later or evaluation, just as the mechanism of tag filtering.</p>
<ul>
<li>Optimization, pre-calculate the filtering result when build consume queue</li>
@@ -384,15 +384,15 @@
<li>decode message properties, once every consumer subscribed same topic pull message.</li>
</ol>
-<p><code class="highlighter-rouge">BloomFilter</code> and pre-calculation are adopted to optimize the situation:</p>
+<p><code class="language-plaintext highlighter-rouge">BloomFilter</code> and pre-calculation are adopted to optimize the situation:</p>
<p><img src="/assets/images/blog/filter_build_cq_apache.png" alt="screenshot" /></p>
<ol>
- <li>Every consumer has been asigned some bit position of <code class="highlighter-rouge">BloomFilter</code> when register to broker.</li>
- <li>When broker build queue after message into <code class="highlighter-rouge">CommitLog</code>, the consumer’s filtering result would be calculated, and all resuls are assembled as a <code class="highlighter-rouge">BitsArray</code> saved in <code class="highlighter-rouge">ConsumeQueueExt</code>.</li>
- <li><code class="highlighter-rouge">ConsumeQueueExt</code> is a store file linked to <code class="highlighter-rouge">ConsumeQueue</code>, <code class="highlighter-rouge">ConsumeQueue</code> could find the data by the <code class="highlighter-rouge">tagsCode</code> whitch is already replaced by the address(for compitable, the range is Long.MIN_VALUE to Integer.MIN_VALUE) generated by <code class="highlighter-rouge">ConsumeQueueExt</code>.</li>
- <li><code class="highlighter-rouge">ExpressionMessageFilter</code> could use the <code class="highlighter-rouge">BitsArray</code> to check whether the message is matched. Because of BloomFilter’s collision, it also need to decode properties to do calculation for matched message(may could be reduced by check the collision, not include in this edition).</li>
+ <li>Every consumer has been asigned some bit position of <code class="language-plaintext highlighter-rouge">BloomFilter</code> when register to broker.</li>
+ <li>When broker build queue after message into <code class="language-plaintext highlighter-rouge">CommitLog</code>, the consumer’s filtering result would be calculated, and all resuls are assembled as a <code class="language-plaintext highlighter-rouge">BitsArray</code> saved in <code class="language-plaintext highlighter-rouge">ConsumeQueueExt</code>.</li>
+ <li><code class="language-plaintext highlighter-rouge">ConsumeQueueExt</code> is a store file linked to <code class="language-plaintext highlighter-rouge">ConsumeQueue</code>, <code class="language-plaintext highlighter-rouge">ConsumeQueue</code> could find the data by the <code class="language-plaintext highlighter-rouge">tagsCode</code> whitch is already replaced by the address(for compitable, the range is Long.MIN_VALUE to Integer.MIN_VALUE) generated by <code class="language-plaint [...]
+ <li><code class="language-plaintext highlighter-rouge">ExpressionMessageFilter</code> could use the <code class="language-plaintext highlighter-rouge">BitsArray</code> to check whether the message is matched. Because of BloomFilter’s collision, it also need to decode properties to do calculation for matched message(may could be reduced by check the collision, not include in this edition).</li>
</ol>
<p>This optimization is suitable for:</p>
@@ -415,7 +415,7 @@
<p>Only push consumer could filter message by SQL92 expression in this edition, the interface is:</p>
-<p><code class="highlighter-rouge">public void subscribe(final String topic, final MessageSelector messageSelector)</code></p>
+<p><code class="language-plaintext highlighter-rouge">public void subscribe(final String topic, final MessageSelector messageSelector)</code></p>
<h3 id="performance-comparison">Performance Comparison</h3>
diff --git a/content/rocketmq/four-methods-to-feed-name-server-address-list/index.html b/content/rocketmq/four-methods-to-feed-name-server-address-list/index.html
index 5f2bfeb..cf24376 100644
--- a/content/rocketmq/four-methods-to-feed-name-server-address-list/index.html
+++ b/content/rocketmq/four-methods-to-feed-name-server-address-list/index.html
@@ -325,39 +325,39 @@ In Apache RocketMQ, this can be done in four ways.</p>
<li>
<p>Programmatic Way</p>
- <p>For broker, we may specify <code class="highlighter-rouge">namesrvAddr=name-server-ip1:port;name-server-ip2:port</code> in broker configuration file.</p>
+ <p>For broker, we may specify <code class="language-plaintext highlighter-rouge">namesrvAddr=name-server-ip1:port;name-server-ip2:port</code> in broker configuration file.</p>
<p>For producers and consumers, we may feed name server address list to them as follows:</p>
- <p><code class="highlighter-rouge">
-DefaultMQProducer producer = new DefaultMQProducer("please_rename_unique_group_name");
-producer.setNamesrvAddr("name-server1-ip:port;name-server2-ip:port");</code></p>
+ <p>`
+DefaultMQProducer producer = new DefaultMQProducer(“please_rename_unique_group_name”);
+producer.setNamesrvAddr(“name-server1-ip:port;name-server2-ip:port”);`</p>
- <p><code class="highlighter-rouge">
-DefaultMQPushConsumer consumer = new DefaultMQPushConsumer("please_rename_unique_group_name");
-consumer.setNamesrvAddr("name-server1-ip:port;name-server2-ip:port");</code></p>
+ <p>`
+DefaultMQPushConsumer consumer = new DefaultMQPushConsumer(“please_rename_unique_group_name”);
+consumer.setNamesrvAddr(“name-server1-ip:port;name-server2-ip:port”);`</p>
<p>If you use admin command line from shell, you may specify this way:
-<code class="highlighter-rouge">sh mqadmin command-name -n name-server-ip1:port;name-server-ip2:port -X OTHER-OPTION</code></p>
+<code class="language-plaintext highlighter-rouge">sh mqadmin command-name -n name-server-ip1:port;name-server-ip2:port -X OTHER-OPTION</code></p>
<p>a simple example is:
-<code class="highlighter-rouge">sh mqadmin -n localhost:9876 clusterList</code>
+<code class="language-plaintext highlighter-rouge">sh mqadmin -n localhost:9876 clusterList</code>
assuming to query cluster info on the name server node.</p>
<p>If integrating admin tool into your own dashboard, you may
-<code class="highlighter-rouge">DefaultMQAdminExt defaultMQAdminExt = new DefaultMQAdminExt("please_rename_unique_group_name");
+<code class="language-plaintext highlighter-rouge">DefaultMQAdminExt defaultMQAdminExt = new DefaultMQAdminExt("please_rename_unique_group_name");
defaultMQAdminExt.setNamesrvAddr("name-server1-ip:port;name-server2-ip:port");</code></p>
</li>
<li>
<p>Java Options</p>
<p>Name server address list may also be fed to your application through specifying the sequel java option
- <code class="highlighter-rouge">rocketmq.namesrv.addr</code> before launching.</p>
+ <code class="language-plaintext highlighter-rouge">rocketmq.namesrv.addr</code> before launching.</p>
</li>
<li>
<p>Environment Variable</p>
- <p>You can export <code class="highlighter-rouge">NAMESRV_ADDR</code> environment variable. Brokers and clients will examine and use its value if set.</p>
+ <p>You can export <code class="language-plaintext highlighter-rouge">NAMESRV_ADDR</code> environment variable. Brokers and clients will examine and use its value if set.</p>
</li>
<li>
<p>HTTP Endpoint</p>
@@ -368,10 +368,10 @@ assuming to query cluster info on the name server node.</p>
<p>On default, the end point is:</p>
- <p><code class="highlighter-rouge">http://jmenv.tbsite.net:8080/rocketmq/nsaddr</code></p>
+ <p><code class="language-plaintext highlighter-rouge">http://jmenv.tbsite.net:8080/rocketmq/nsaddr</code></p>
- <p>You may override <code class="highlighter-rouge">jmenv.tbsite.net</code> by this java option: <code class="highlighter-rouge">rocketmq.namesrv.domain</code>,
- You may also override <code class="highlighter-rouge">nsaddr</code> part by this java option: <code class="highlighter-rouge">rocketmq.namesrv.domain.subgroup</code></p>
+ <p>You may override <code class="language-plaintext highlighter-rouge">jmenv.tbsite.net</code> by this java option: <code class="language-plaintext highlighter-rouge">rocketmq.namesrv.domain</code>,
+ You may also override <code class="language-plaintext highlighter-rouge">nsaddr</code> part by this java option: <code class="language-plaintext highlighter-rouge">rocketmq.namesrv.domain.subgroup</code></p>
<p>If you are running Apache RocketMQ in production, this method is recommended because it gives you maximum flexibility
– you can dynamically add or remove name server nodes without necessity of rebooting your brokers and clients
@@ -384,7 +384,7 @@ assuming to query cluster info on the name server node.</p>
<p>Priority</p>
<p>Methods introduced first take precedence over the latter, namely, <br />
- <code class="highlighter-rouge">Programmatic Way > Java Options > Environment Variable > HTTP Endpoint</code></p>
+ <code class="language-plaintext highlighter-rouge">Programmatic Way > Java Options > Environment Variable > HTTP Endpoint</code></p>
</li>
</ul>
diff --git a/content/sitemap.xml b/content/sitemap.xml
index cd44af5..c9a6b97 100644
--- a/content/sitemap.xml
+++ b/content/sitemap.xml
@@ -2,135 +2,135 @@
<urlset xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd" xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>/about/team/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/about/contact/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/about/rewards/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/quick-start/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/motivation/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/core-concept/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/cli-admin-tool/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/cluster-deployment/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/pull-request/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/code-guidelines/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/documentation/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/faq/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/release-manual</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/dowloading/releases/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/roadmap/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/batch-example/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/broadcast-example/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/rmq-deployment/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/order-example/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/rmq-arc/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/schedule-example/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/simple-example/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/filter-by-sql92-example/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/logappender-example/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/openmessaging-example/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/system-config/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/how-to-contribute/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/transaction-example/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/best-practice-broker/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/best-practice-consumer/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/create-pull-request/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/best-practice-namesvr/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/docs/best-practice-producer/</loc>
-<lastmod>2021-08-09T15:32:06+08:00</lastmod>
+<lastmod>2021-08-11T17:46:15+08:00</lastmod>
</url>
<url>
<loc>/rocketmq/how-to-support-more-queues-in-rocketmq/</loc>
@@ -416,10 +416,10 @@
</url>
<url>
<loc>/assets/attachment/launch-rocketmq-code-marathon.pdf</loc>
-<lastmod>2019-08-02T19:48:38+08:00</lastmod>
+<lastmod>2021-06-08T18:08:32+08:00</lastmod>
</url>
<url>
<loc>/assets/attachment/launch-second-rocketmq-code-marathon.pdf</loc>
-<lastmod>2019-08-02T19:48:38+08:00</lastmod>
+<lastmod>2021-06-08T18:08:32+08:00</lastmod>
</url>
</urlset>