YUKI Hiroshi
null+****@clear*****
Thu May 29 22:06:30 JST 2014
YUKI Hiroshi 2014-05-29 22:06:30 +0900 (Thu, 29 May 2014) New Revision: 19bb6badb5c9487b1834a0124444a918046bf40d https://github.com/droonga/droonga.org/commit/19bb6badb5c9487b1834a0124444a918046bf40d Message: Add steps to confirm Modified files: _po/ja/tutorial/1.0.3/add-replica/index.po _po/ja/tutorial/1.0.4/add-replica/index.po ja/tutorial/1.0.3/add-replica/index.md ja/tutorial/1.0.4/add-replica/index.md tutorial/1.0.3/add-replica/index.md tutorial/1.0.4/add-replica/index.md Modified: _po/ja/tutorial/1.0.3/add-replica/index.po (+66 -0) =================================================================== --- _po/ja/tutorial/1.0.3/add-replica/index.po 2014-05-29 21:39:22 +0900 (834c66c) +++ _po/ja/tutorial/1.0.3/add-replica/index.po 2014-05-29 22:06:30 +0900 (e420d4f) @@ -196,6 +196,36 @@ msgstr "" " * 1つのreplicaを含む新しいクラスタ。以下、*「beta」*と仮称します。\n" " * `192.168.0.12`" +msgid "You can confirm that, via the status file `live-nodes.json` on each node:" +msgstr "この事は、各ノード上にあるステータスファイル `live-nodes.json` を見ると確認できます:" + +msgid "" +"~~~\n" +"(on 192.168.0.10, 192.168.0.11)\n" +"# cat ~/droonga/state/live-nodes.json\n" +"{\n" +" \"192.168.0.10:10031/droonga\": {\n" +" \"serfAddress\": \"192.168.100.52:7946\"\n" +" },\n" +" \"192.168.0.11:10031/droonga\": {\n" +" \"serfAddress\": \"192.168.100.50:7946\"\n" +" }\n" +"}\n" +"~~~" +msgstr "" + +msgid "" +"~~~\n" +"(on 192.168.0.12)\n" +"# cat ~/droonga/state/live-nodes.json\n" +"{\n" +" \"192.168.0.12:10031/droonga\": {\n" +" \"serfAddress\": \"192.168.100.51:7946\"\n" +" }\n" +"}\n" +"~~~" +msgstr "" + msgid "### Suspend inpouring of \"write\" requests" msgstr "### 書き込みを伴うリクエストの流入を一時的に停止する" @@ -328,6 +358,24 @@ msgstr "" " * `192.168.0.12`" msgid "" +"~~~\n" +"(on 192.168.0.12)\n" +"# cat ~/droonga/state/live-nodes.json\n" +"{\n" +" \"192.168.0.10:10031/droonga\": {\n" +" \"serfAddress\": \"192.168.100.52:7946\"\n" +" },\n" +" \"192.168.0.11:10031/droonga\": {\n" +" \"serfAddress\": \"192.168.100.50:7946\"\n" +" },\n" +" \"192.168.0.12:10031/droonga\": {\n" +" \"serfAddress\": \"192.168.100.51:7946\"\n" +" }\n" +"}\n" +"~~~" +msgstr "" + +msgid "" "Note that the temporary cluster named \"beta\" is gone.\n" "And, the new node `192.168.0.12` knows the cluster charlie includes three node" "s, other two existing nodes don't know that.\n" @@ -368,6 +416,24 @@ msgstr "" " * `192.168.0.12`" msgid "" +"~~~\n" +"(on 192.168.0.10, 192.168.0.11, 192.168.0.12)\n" +"# cat ~/droonga/state/live-nodes.json\n" +"{\n" +" \"192.168.0.10:10031/droonga\": {\n" +" \"serfAddress\": \"192.168.100.52:7946\"\n" +" },\n" +" \"192.168.0.11:10031/droonga\": {\n" +" \"serfAddress\": \"192.168.100.50:7946\"\n" +" },\n" +" \"192.168.0.12:10031/droonga\": {\n" +" \"serfAddress\": \"192.168.100.51:7946\"\n" +" }\n" +"}\n" +"~~~" +msgstr "" + +msgid "" "Note that the old cluster named \"alpha\" is gone.\n" "Now the new cluster \"charlie\" with three replicas works perfectly, instead of " "the old one with two replicas." Modified: _po/ja/tutorial/1.0.4/add-replica/index.po (+66 -0) =================================================================== --- _po/ja/tutorial/1.0.4/add-replica/index.po 2014-05-29 21:39:22 +0900 (834c66c) +++ _po/ja/tutorial/1.0.4/add-replica/index.po 2014-05-29 22:06:30 +0900 (e420d4f) @@ -196,6 +196,36 @@ msgstr "" " * 1つのreplicaを含む新しいクラスタ。以下、*「beta」*と仮称します。\n" " * `192.168.0.12`" +msgid "You can confirm that, via the status file `live-nodes.json` on each node:" +msgstr "この事は、各ノード上にあるステータスファイル `live-nodes.json` を見ると確認できます:" + +msgid "" +"~~~\n" +"(on 192.168.0.10, 192.168.0.11)\n" +"# cat ~/droonga/state/live-nodes.json\n" +"{\n" +" \"192.168.0.10:10031/droonga\": {\n" +" \"serfAddress\": \"192.168.100.52:7946\"\n" +" },\n" +" \"192.168.0.11:10031/droonga\": {\n" +" \"serfAddress\": \"192.168.100.50:7946\"\n" +" }\n" +"}\n" +"~~~" +msgstr "" + +msgid "" +"~~~\n" +"(on 192.168.0.12)\n" +"# cat ~/droonga/state/live-nodes.json\n" +"{\n" +" \"192.168.0.12:10031/droonga\": {\n" +" \"serfAddress\": \"192.168.100.51:7946\"\n" +" }\n" +"}\n" +"~~~" +msgstr "" + msgid "### Suspend inpouring of \"write\" requests" msgstr "### 書き込みを伴うリクエストの流入を一時的に停止する" @@ -328,6 +358,24 @@ msgstr "" " * `192.168.0.12`" msgid "" +"~~~\n" +"(on 192.168.0.12)\n" +"# cat ~/droonga/state/live-nodes.json\n" +"{\n" +" \"192.168.0.10:10031/droonga\": {\n" +" \"serfAddress\": \"192.168.100.52:7946\"\n" +" },\n" +" \"192.168.0.11:10031/droonga\": {\n" +" \"serfAddress\": \"192.168.100.50:7946\"\n" +" },\n" +" \"192.168.0.12:10031/droonga\": {\n" +" \"serfAddress\": \"192.168.100.51:7946\"\n" +" }\n" +"}\n" +"~~~" +msgstr "" + +msgid "" "Note that the temporary cluster named \"beta\" is gone.\n" "And, the new node `192.168.0.12` knows the cluster charlie includes three node" "s, other two existing nodes don't know that.\n" @@ -368,6 +416,24 @@ msgstr "" " * `192.168.0.12`" msgid "" +"~~~\n" +"(on 192.168.0.10, 192.168.0.11, 192.168.0.12)\n" +"# cat ~/droonga/state/live-nodes.json\n" +"{\n" +" \"192.168.0.10:10031/droonga\": {\n" +" \"serfAddress\": \"192.168.100.52:7946\"\n" +" },\n" +" \"192.168.0.11:10031/droonga\": {\n" +" \"serfAddress\": \"192.168.100.50:7946\"\n" +" },\n" +" \"192.168.0.12:10031/droonga\": {\n" +" \"serfAddress\": \"192.168.100.51:7946\"\n" +" }\n" +"}\n" +"~~~" +msgstr "" + +msgid "" "Note that the old cluster named \"alpha\" is gone.\n" "Now the new cluster \"charlie\" with three replicas works perfectly, instead of " "the old one with two replicas." Modified: ja/tutorial/1.0.3/add-replica/index.md (+75 -0) =================================================================== --- ja/tutorial/1.0.3/add-replica/index.md 2014-05-29 21:39:22 +0900 (f9d6c55) +++ ja/tutorial/1.0.3/add-replica/index.md 2014-05-29 22:06:30 +0900 (b22aa9c) @@ -101,6 +101,31 @@ Droongaのノードの集合には、「replica」と「slice」という2つの * 1つのreplicaを含む新しいクラスタ。以下、*「beta」*と仮称します。 * `192.168.0.12` +この事は、各ノード上にあるステータスファイル `live-nodes.json` を見ると確認できます: + +~~~ +(on 192.168.0.10, 192.168.0.11) +# cat ~/droonga/state/live-nodes.json +{ + "192.168.0.10:10031/droonga": { + "serfAddress": "192.168.100.52:7946" + }, + "192.168.0.11:10031/droonga": { + "serfAddress": "192.168.100.50:7946" + } +} +~~~ + +~~~ +(on 192.168.0.12) +# cat ~/droonga/state/live-nodes.json +{ + "192.168.0.12:10031/droonga": { + "serfAddress": "192.168.100.51:7946" + } +} +~~~ + ### 書き込みを伴うリクエストの流入を一時的に停止する クラスタ alpha とクラスタ beta のデータを完全に同期する必要があるので、データの複製を始める前に、クラスタ alphaへのデータの書き込みを行うリクエストの流入を一時停止する必要があります。 @@ -165,10 +190,42 @@ cronjobとして実行されるバッチスクリプトによって `load` コ * `192.168.0.11` * `192.168.0.12` +この事は、各ノード上にあるステータスファイル `live-nodes.json` を見ると確認できます: + +~~~ +(on 192.168.0.10, 192.168.0.11) +# cat ~/droonga/state/live-nodes.json +{ + "192.168.0.10:10031/droonga": { + "serfAddress": "192.168.100.52:7946" + }, + "192.168.0.11:10031/droonga": { + "serfAddress": "192.168.100.50:7946" + } +} +~~~ + +~~~ +(on 192.168.0.12) +# cat ~/droonga/state/live-nodes.json +{ + "192.168.0.10:10031/droonga": { + "serfAddress": "192.168.100.52:7946" + }, + "192.168.0.11:10031/droonga": { + "serfAddress": "192.168.100.50:7946" + }, + "192.168.0.12:10031/droonga": { + "serfAddress": "192.168.100.51:7946" + } +} +~~~ + 「beta」と仮称した一時的なクラスタが姿を消している事に注意してください。 この時、新しいノード `192.168.0.12` はクラスタ charlie が3つのノードを含んでいる事を知っていますが、他の2つの既存のノードはその事を知りません。 既存の2つのノードは、自分自身が属しているクラスタ内にいるノードは2つだけだと認識しているため、流入してきたリクエストは、新しいノード `192.168.0.12` へはまだ配送されません。 + 次に、新しい `catalog.json` を`192.168.0.12` から他のノードにコピーします。 (on 192.168.0.12) @@ -184,6 +241,24 @@ cronjobとして実行されるバッチスクリプトによって `load` コ * `192.168.0.11` * `192.168.0.12` +この事は、各ノード上にあるステータスファイル `live-nodes.json` を見ると確認できます: + +~~~ +(on 192.168.0.10, 192.168.0.11, 192.168.0.12) +# cat ~/droonga/state/live-nodes.json +{ + "192.168.0.10:10031/droonga": { + "serfAddress": "192.168.100.52:7946" + }, + "192.168.0.11:10031/droonga": { + "serfAddress": "192.168.100.50:7946" + }, + "192.168.0.12:10031/droonga": { + "serfAddress": "192.168.100.51:7946" + } +} +~~~ + 「alpha」と仮称した古いクラスタが姿を消している事に注意してください。 この時、2つのreplicaからなる古いクラスタの代わりとして、新しいクラスタ「charlie」は3つのreplicaのもとで完璧に動作しています。 Modified: ja/tutorial/1.0.4/add-replica/index.md (+74 -0) =================================================================== --- ja/tutorial/1.0.4/add-replica/index.md 2014-05-29 21:39:22 +0900 (460abee) +++ ja/tutorial/1.0.4/add-replica/index.md 2014-05-29 22:06:30 +0900 (fe00fc6) @@ -101,6 +101,31 @@ Droongaのノードの集合には、「replica」と「slice」という2つの * 1つのreplicaを含む新しいクラスタ。以下、*「beta」*と仮称します。 * `192.168.0.12` +この事は、各ノード上にあるステータスファイル `live-nodes.json` を見ると確認できます: + +~~~ +(on 192.168.0.10, 192.168.0.11) +# cat ~/droonga/state/live-nodes.json +{ + "192.168.0.10:10031/droonga": { + "serfAddress": "192.168.100.52:7946" + }, + "192.168.0.11:10031/droonga": { + "serfAddress": "192.168.100.50:7946" + } +} +~~~ + +~~~ +(on 192.168.0.12) +# cat ~/droonga/state/live-nodes.json +{ + "192.168.0.12:10031/droonga": { + "serfAddress": "192.168.100.51:7946" + } +} +~~~ + ### 書き込みを伴うリクエストの流入を一時的に停止する クラスタ alpha とクラスタ beta のデータを完全に同期する必要があるので、データの複製を始める前に、クラスタ alphaへのデータの書き込みを行うリクエストの流入を一時停止する必要があります。 @@ -165,6 +190,37 @@ cronjobとして実行されるバッチスクリプトによって `load` コ * `192.168.0.11` * `192.168.0.12` +この事は、各ノード上にあるステータスファイル `live-nodes.json` を見ると確認できます: + +~~~ +(on 192.168.0.10, 192.168.0.11) +# cat ~/droonga/state/live-nodes.json +{ + "192.168.0.10:10031/droonga": { + "serfAddress": "192.168.100.52:7946" + }, + "192.168.0.11:10031/droonga": { + "serfAddress": "192.168.100.50:7946" + } +} +~~~ + +~~~ +(on 192.168.0.12) +# cat ~/droonga/state/live-nodes.json +{ + "192.168.0.10:10031/droonga": { + "serfAddress": "192.168.100.52:7946" + }, + "192.168.0.11:10031/droonga": { + "serfAddress": "192.168.100.50:7946" + }, + "192.168.0.12:10031/droonga": { + "serfAddress": "192.168.100.51:7946" + } +} +~~~ + 「beta」と仮称した一時的なクラスタが姿を消している事に注意してください。 この時、新しいノード `192.168.0.12` はクラスタ charlie が3つのノードを含んでいる事を知っていますが、他の2つの既存のノードはその事を知りません。 既存の2つのノードは、自分自身が属しているクラスタ内にいるノードは2つだけだと認識しているため、流入してきたリクエストは、新しいノード `192.168.0.12` へはまだ配送されません。 @@ -184,6 +240,24 @@ cronjobとして実行されるバッチスクリプトによって `load` コ * `192.168.0.11` * `192.168.0.12` +この事は、各ノード上にあるステータスファイル `live-nodes.json` を見ると確認できます: + +~~~ +(on 192.168.0.10, 192.168.0.11, 192.168.0.12) +# cat ~/droonga/state/live-nodes.json +{ + "192.168.0.10:10031/droonga": { + "serfAddress": "192.168.100.52:7946" + }, + "192.168.0.11:10031/droonga": { + "serfAddress": "192.168.100.50:7946" + }, + "192.168.0.12:10031/droonga": { + "serfAddress": "192.168.100.51:7946" + } +} +~~~ + 「alpha」と仮称した古いクラスタが姿を消している事に注意してください。 この時、2つのreplicaからなる古いクラスタの代わりとして、新しいクラスタ「charlie」は3つのreplicaのもとで完璧に動作しています。 Modified: tutorial/1.0.3/add-replica/index.md (+75 -0) =================================================================== --- tutorial/1.0.3/add-replica/index.md 2014-05-29 21:39:22 +0900 (3125413) +++ tutorial/1.0.3/add-replica/index.md 2014-05-29 22:06:30 +0900 (1d385a9) @@ -95,6 +95,31 @@ Then there are two separate Droonga clusters on this time. Let's give a name *"beta"* to it, for now. * `192.168.0.12` +You can confirm that, via the status file `live-nodes.json` on each node: + +~~~ +(on 192.168.0.10, 192.168.0.11) +# cat ~/droonga/state/live-nodes.json +{ + "192.168.0.10:10031/droonga": { + "serfAddress": "192.168.100.52:7946" + }, + "192.168.0.11:10031/droonga": { + "serfAddress": "192.168.100.50:7946" + } +} +~~~ + +~~~ +(on 192.168.0.12) +# cat ~/droonga/state/live-nodes.json +{ + "192.168.0.12:10031/droonga": { + "serfAddress": "192.168.100.51:7946" + } +} +~~~ + ### Suspend inpouring of "write" requests Before starting duplication of data, you must suspend inpouring of "write" requests to the cluster alpha, because we have to synchronize data in clusters alpha and beta completely. @@ -161,10 +186,42 @@ Then there are two overlapping Droonga clusters theoretically on this time. * `192.168.0.11` * `192.168.0.12` +You can confirm that, via the status file `live-nodes.json` on each node: + +~~~ +(on 192.168.0.10, 192.168.0.11) +# cat ~/droonga/state/live-nodes.json +{ + "192.168.0.10:10031/droonga": { + "serfAddress": "192.168.100.52:7946" + }, + "192.168.0.11:10031/droonga": { + "serfAddress": "192.168.100.50:7946" + } +} +~~~ + +~~~ +(on 192.168.0.12) +# cat ~/droonga/state/live-nodes.json +{ + "192.168.0.10:10031/droonga": { + "serfAddress": "192.168.100.52:7946" + }, + "192.168.0.11:10031/droonga": { + "serfAddress": "192.168.100.50:7946" + }, + "192.168.0.12:10031/droonga": { + "serfAddress": "192.168.100.51:7946" + } +} +~~~ + Note that the temporary cluster named "beta" is gone. And, the new node `192.168.0.12` knows the cluster charlie includes three nodes, other two existing nodes don't know that. Because both two existing nodes think that there are only them in the cluster they belong to, any incoming request to them never delivered to the new replica `192.168.0.12` yet. + Next, copy new `catalog.json` from `192.168.0.12` to others. (on 192.168.0.12) @@ -180,6 +237,24 @@ Then there is just one Droonga clusters on this time. * `192.168.0.11` * `192.168.0.12` +You can confirm that, via the status file `live-nodes.json` on each node: + +~~~ +(on 192.168.0.10, 192.168.0.11, 192.168.0.12) +# cat ~/droonga/state/live-nodes.json +{ + "192.168.0.10:10031/droonga": { + "serfAddress": "192.168.100.52:7946" + }, + "192.168.0.11:10031/droonga": { + "serfAddress": "192.168.100.50:7946" + }, + "192.168.0.12:10031/droonga": { + "serfAddress": "192.168.100.51:7946" + } +} +~~~ + Note that the old cluster named "alpha" is gone. Now the new cluster "charlie" with three replicas works perfectly, instead of the old one with two replicas. Modified: tutorial/1.0.4/add-replica/index.md (+74 -0) =================================================================== --- tutorial/1.0.4/add-replica/index.md 2014-05-29 21:39:22 +0900 (3125413) +++ tutorial/1.0.4/add-replica/index.md 2014-05-29 22:06:30 +0900 (620f316) @@ -95,6 +95,31 @@ Then there are two separate Droonga clusters on this time. Let's give a name *"beta"* to it, for now. * `192.168.0.12` +You can confirm that, via the status file `live-nodes.json` on each node: + +~~~ +(on 192.168.0.10, 192.168.0.11) +# cat ~/droonga/state/live-nodes.json +{ + "192.168.0.10:10031/droonga": { + "serfAddress": "192.168.100.52:7946" + }, + "192.168.0.11:10031/droonga": { + "serfAddress": "192.168.100.50:7946" + } +} +~~~ + +~~~ +(on 192.168.0.12) +# cat ~/droonga/state/live-nodes.json +{ + "192.168.0.12:10031/droonga": { + "serfAddress": "192.168.100.51:7946" + } +} +~~~ + ### Suspend inpouring of "write" requests Before starting duplication of data, you must suspend inpouring of "write" requests to the cluster alpha, because we have to synchronize data in clusters alpha and beta completely. @@ -161,6 +186,37 @@ Then there are two overlapping Droonga clusters theoretically on this time. * `192.168.0.11` * `192.168.0.12` +You can confirm that, via the status file `live-nodes.json` on each node: + +~~~ +(on 192.168.0.10, 192.168.0.11) +# cat ~/droonga/state/live-nodes.json +{ + "192.168.0.10:10031/droonga": { + "serfAddress": "192.168.100.52:7946" + }, + "192.168.0.11:10031/droonga": { + "serfAddress": "192.168.100.50:7946" + } +} +~~~ + +~~~ +(on 192.168.0.12) +# cat ~/droonga/state/live-nodes.json +{ + "192.168.0.10:10031/droonga": { + "serfAddress": "192.168.100.52:7946" + }, + "192.168.0.11:10031/droonga": { + "serfAddress": "192.168.100.50:7946" + }, + "192.168.0.12:10031/droonga": { + "serfAddress": "192.168.100.51:7946" + } +} +~~~ + Note that the temporary cluster named "beta" is gone. And, the new node `192.168.0.12` knows the cluster charlie includes three nodes, other two existing nodes don't know that. Because both two existing nodes think that there are only them in the cluster they belong to, any incoming request to them never delivered to the new replica `192.168.0.12` yet. @@ -180,6 +236,24 @@ Then there is just one Droonga clusters on this time. * `192.168.0.11` * `192.168.0.12` +You can confirm that, via the status file `live-nodes.json` on each node: + +~~~ +(on 192.168.0.10, 192.168.0.11, 192.168.0.12) +# cat ~/droonga/state/live-nodes.json +{ + "192.168.0.10:10031/droonga": { + "serfAddress": "192.168.100.52:7946" + }, + "192.168.0.11:10031/droonga": { + "serfAddress": "192.168.100.50:7946" + }, + "192.168.0.12:10031/droonga": { + "serfAddress": "192.168.100.51:7946" + } +} +~~~ + Note that the old cluster named "alpha" is gone. Now the new cluster "charlie" with three replicas works perfectly, instead of the old one with two replicas. -------------- next part -------------- HTML����������������������������...Descargar
