To join an existing cluster, you must specify at least:
- The nameof the cluster
- The
host:portof another node in the cluster you are joining
- SQL
- JSON
- PHP
- Python
- javascript
- Java
- C#
JOIN CLUSTER posts AT '10.12.1.35:9312'{u'error': u'', u'total': 0, u'warning': u''}In most cases, the above is sufficient when there is a single replication cluster. However, if you are creating multiple replication clusters, you must also set the path and ensure that the directory is available.
- SQL
JOIN CLUSTER c2 at '127.0.0.1:10201' 'c2' as pathA node joins a cluster by obtaining data from a specified node and, if successful, updates the node lists across all other cluster nodes in the same way as if it was done manually through ALTER CLUSTER ... UPDATE nodes. This list is used to re-join nodes to the cluster upon restart.
There are two lists of nodes:
1.cluster_<name>_nodes_set: used to re-join nodes to the cluster upon restart. It is updated across all nodes in the same way as ALTER CLUSTER ... UPDATE nodes does. JOIN CLUSTER command performs this update automatically. The Cluster status displays this list as cluster_<name>_nodes_set.
2. cluster_<name>_nodes_view: this list contains all active nodes used for replication and does not require manual management. ALTER CLUSTER ... UPDATE nodes actually copies this list of nodes to the list of nodes used to re-join upon restart. The Cluster status displays this list as cluster_<name>_nodes_view.
When nodes are located in different network segments or data centers, the nodes option may be set explicitly. This minimizes traffic between nodes and utilizes gateway nodes for intercommunication between data centers. The following code joins an existing cluster using the nodes option.
Note: The cluster
cluster_<name>_nodes_setlist is not updated automatically when this syntax is used. To update it, use ALTER CLUSTER ... UPDATE nodes.
- SQL
- JSON
- PHP
- Python
- javascript
- Java
- C#
JOIN CLUSTER click_query 'clicks_mirror1:9312;clicks_mirror2:9312;clicks_mirror3:9312' as nodes{u'error': u'', u'total': 0, u'warning': u''}The JOIN CLUSTER command works synchronously and completes as soon as the node receives all data from the other nodes in the cluster and is in sync with them.
The DELETE CLUSTER statement removes the specified cluster with its name. Once the cluster is deleted, it is removed from all nodes, but its tables remain intact and become active local non-replicated tables.
- SQL
- JSON
- PHP
- Python
- javascript
- Java
- C#
DELETE CLUSTER click_query{u'error': u'', u'total': 0, u'warning': u''}ALTER CLUSTER <cluster_name> ADD <table_name> adds an existing local table to the cluster. The node that receives the ALTER query sends the table to the other nodes in the cluster. All the local tables with the same name on the other nodes of the cluster are replaced with the new table.
Once the table is replicated, write statements can be performed on any node, but the table name must be prefixed with the cluster name, like INSERT INTO <clusterName>:<table_name>.
- SQL
- JSON
- PHP
- Python
- javascript
- Java
- C#
ALTER CLUSTER click_query ADD clicks_daily_index{u'error': u'', u'total': 0, u'warning': u''}ALTER CLUSTER <cluster_name> DROP <table_name> forgets about a local table, meaning it does not remove the table files on the nodes, but rather just makes it an inactive, non-replicated table.
Once a table is removed from a cluster, it becomes a local table, and write statements must use just the table name, like INSERT INTO <table_name>, without the cluster prefix.
- SQL
- JSON
- PHP
- Python
- javascript
- Java
- C#
ALTER CLUSTER posts DROP weekly_index{u'error': u'', u'total': 0, u'warning': u''}