[Groonga-commit] droonga/wikipedia-search.wiki at ddc4668 [master] Updated ノンストップでノードを追加する場面の検証手順 (markdown)

Zurück zum Archiv-Index

YUKI Piro Hiroshi null+****@clear*****
Wed Apr 8 14:00:03 JST 2015


YUKI "Piro" Hiroshi	2015-04-08 14:00:03 +0900 (Wed, 08 Apr 2015)

  New Revision: ddc4668be5a55836555ca0527927a00214b7ed1f
  https://github.com/droonga/wikipedia-search/wiki/%E3%83%8E%E3%83%B3%E3%82%B9%E3%83%88%E3%83%83%E3%83%97%E3%81%A7%E3%83%8E%E3%83%BC%E3%83%89%E3%82%92%E8%BF%BD%E5%8A%A0%E3%81%99%E3%82%8B%E5%A0%B4%E9%9D%A2%E3%81%AE%E6%A4%9C%E8%A8%BC%E6%89%8B%E9%A0%86/ddc4668be5a55836555ca0527927a00214b7ed1f

  Message:
    Updated ノンストップでノードを追加する場面の検証手順 (markdown)

  Modified files:
    ノンストップでノードを追加する場面の検証手順.md

  Modified: ノンストップでノードを追加する場面の検証手順.md (+12 -11)
===================================================================
--- ノンストップでノードを追加する場面の検証手順.md    2015-04-07 18:49:56 +0900 (14eb049)
+++ ノンストップでノードを追加する場面の検証手順.md    2015-04-08 14:00:03 +0900 (586fcbe)
@@ -200,16 +200,17 @@ $SOURCE_SUDO service td-agent start
 
 ~~~
 serf="sudo -u droonga-engine -H /home/droonga-engine/droonga/serf"
+triple_logger() { for count in 0 1 2; do logger "$1 ($count)"; done; }
 ~~~
 
 まず新ノードをjoinさせる
 
 ~~~
-logger "0: start join"
+triple_logger "0: start join"
 $serf query -rpc-addr node2:7373 change_role '{"node":"node2:10031/droonga","role":"absorb-destination"}'
-logger "1: role of the joining node is changed"
+triple_logger "1: role of the joining node is changed"
 $serf query -rpc-addr node2:7373 join '{"node":"node2:10031/droonga","type":"replica","source":"node1:10031/droonga","dataset":"Default"}'
-logger "2: other nodes are registered to the joining node"
+triple_logger "2: other nodes are registered to the joining node"
 ~~~
 
 この時点で、droonga-http-server �� node2は、接続先engineが存在しない(認識できていない)。
@@ -219,7 +220,7 @@ logger "2: other nodes are registered to the joining node"
 
 ~~~
 $serf query -rpc-addr node1:7373 add_replicas '{"cluster_id":"8951f1b01583c1ffeb12ed5f4093210d28955988","dataset":"Default","hosts":["node2"]}'
-logger "3: joining node is registered to other nodes"
+triple_logger "3: joining node is registered to other nodes"
 ~~~
 
 これで、各ノードは同一クラスタで、且つ新ノードのみが機能していない状態になる。
@@ -229,24 +230,24 @@ logger "3: joining node is registered to other nodes"
 
 ~~~
 $serf query -rpc-addr node1:7373 change_role '{"node":"node1:10031/droonga","role":"absorb-source"}'
-logger "4: source node is deactivated"
+triple_logger "4: source node is deactivated"
 $serf query -rpc-addr node2:7373 absorb_data '{"node":"node2:10031/droonga","source":"node1:10031/droonga","port":10031,"tag":"droonga","dataset":"Default","messages_per_second":100}'
-logger "5: data copying process is started"
+triple_logger "5: data copying process is started"
 $serf query -rpc-addr node2:7373 report_metadata '{"node":"node2:10031/droonga","key":"absorbing"}'
 
-logger "6: completely copied"
+triple_logger "6: completely copied"
 $serf query -rpc-addr node1:7373 report_metadata '{"node":"node1:10031/droonga","key":"last_processed_message_timestamp"}'
-logger "7: checking last_processed_message_timestamp"
+triple_logger "7: checking last_processed_message_timestamp"
 
 $serf query -rpc-addr node2:7373 accept_messages_newer_than '{"node":"node2:10031/droonga","timestamp":"2015-03-24T04:36:09.423Z"}'
-logger "8: effective_message_timestamp is updated"
+triple_logger "8: effective_message_timestamp is updated"
 ~~~
 
 最後に、roleを戻す。
 
 ~~~
 $serf query -rpc-addr node1:7373 change_role '{"node":"node1:10031/droonga","role":null}'
-logger "9: source node is activated"
+triple_logger "9: source node is activated"
 $serf query -rpc-addr node2:7373 change_role '{"node":"node2:10031/droonga","role":null}'
-logger "10: joining node is activated"
+triple_logger "10: joining node is activated"
 ~~~
-------------- next part --------------
HTML����������������������������...
Download 



More information about the Groonga-commit mailing list
Zurück zum Archiv-Index