[Groonga-commit] droonga/droonga.org at cd2355e [gh-pages] Add examples of tasks should be stopped

Back to archive index

YUKI Hiroshi null+****@clear*****
Wed Apr 29 20:38:40 JST 2015


YUKI Hiroshi	2015-04-29 20:38:40 +0900 (Wed, 29 Apr 2015)

  New Revision: cd2355e2a3e7e5e578b72ee8513e6269f882ba8a
  https://github.com/droonga/droonga.org/commit/cd2355e2a3e7e5e578b72ee8513e6269f882ba8a

  Message:
    Add examples of tasks should be stopped

  Modified files:
    tutorial/1.1.0/add-replica/index.md

  Modified: tutorial/1.1.0/add-replica/index.md (+1 -1)
===================================================================
--- tutorial/1.1.0/add-replica/index.md    2015-04-29 20:37:21 +0900 (6428fd8)
+++ tutorial/1.1.0/add-replica/index.md    2015-04-29 20:38:40 +0900 (dddfae3)
@@ -41,7 +41,7 @@ Here we go!
 *To do "hot-add" (dynamic changing of cluster members without downtime) a new replica to a cluster, you must have two or more existing replicas in the cluster.*
 While the operation is in progress, one of existing replicas becomes the "source" to copy data to the newly added replica, and other replicas provide the service.
 
-If you have only one replica in the cluster, *you must stop any modification on the database until the operation completely finishes*.
+If you have only one replica in the cluster, *you must stop any modification on the database until the operation completely finishes* - cronjob batches, crawlers, and so on.
 Otherwise, databases in each replica can be irregularity.
 This is the list of typical built-in commands which can modify the database:
 
-------------- next part --------------
HTML����������������������������...
Download 



More information about the Groonga-commit mailing list
Back to archive index