ALTER CLUSTER <cluster_name> ADD <table_name>[, <table_name>] adds one or more existing local tables to the cluster. The node that receives the ALTER query sends the table(s) 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(s).
Once the tables are replicated, write statements can be performed on any node, but the table names 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>[, <table_name>] forgets about one or more existing table(s), meaning it does not remove the table(s) files on the nodes, but rather just makes them inactive, non-replicated table(s).
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''}The ALTER CLUSTER <cluster_name> UPDATE nodes statement updates the node lists on each node within the specified cluster to include all active nodes in the cluster. For more information on node lists, see Joining a cluster.
- SQL
- JSON
- PHP
- Python
- javascript
- Java
- C#
ALTER CLUSTER posts UPDATE nodes{u'error': u'', u'total': 0, u'warning': u''}For instance, when the cluster was initially established, the list of nodes used to rejoin the cluster was 10.10.0.1:9312,10.10.1.1:9312. Since then, other nodes joined the cluster and now the active nodes are 10.10.0.1:9312,10.10.1.1:9312,10.15.0.1:9312,10.15.0.3:9312.However, the list of nodes used to rejoin the cluster has not been updated.
To rectify this, you can run the ALTER CLUSTER ... UPDATE nodes statement to copy the list of active nodes to the list of nodes used to rejoin the cluster. After this, the list of nodes used to rejoin the cluster will include all the active nodes in the cluster.
Both lists of nodes can be viewed using the Cluster status statement (cluster_post_nodes_set and cluster_post_nodes_view).
To remove a node from the replication cluster, follow these steps:
- Stop the node
- Remove the information about the cluster from
<data_dir>/manticore.json(usually/var/lib/manticore/manticore.json) on the node that has been stopped. - Run
ALTER CLUSTER cluster_name UPDATE nodeson any other node.
After these steps, the other nodes will forget about the detached node and the detached node will forget about the cluster. This action will not impact the tables in the cluster or on the detached node.
You can view the cluster status information by checking the node status. This can be done using the Node status command, which displays various information about the node, including the cluster status variables.
The output format for the cluster status variables is as follows: cluster_name_variable_name variable_value. Most of the variables are described in the Galera Documentation Status Variables. In addition to these variables, Manticore Search also displays:
- cluster_name - the name of the cluster, as defined in the replication setup
- node_state - the current state of the node:
closed,destroyed,joining,donor,synced - indexes_count - the number of tables managed by the cluster
- indexes - a list of table names managed by the cluster
- nodes_set - the list of nodes in the cluster defined using the
CREATE,JOINorALTER UPDATEcommands - nodes_view - the actual list of nodes in the cluster that the current node can see.
- SQL
- JSON
- PHP
- Python
- javascript
- Java
- C#
SHOW STATUS+----------------------------+-------------------------------------------------------------------------------------+
| Counter | Value |
+----------------------------+-------------------------------------------------------------------------------------+
| cluster_name | post |
| cluster_post_state_uuid | fba97c45-36df-11e9-a84e-eb09d14b8ea7 |
| cluster_post_conf_id | 1 |
| cluster_post_status | primary |
| cluster_post_size | 5 |
| cluster_post_local_index | 0 |
| cluster_post_node_state | synced |
| cluster_post_indexes_count | 2 |
| cluster_post_indexes | pq1,pq_posts |
| cluster_post_nodes_set | 10.10.0.1:9312 |
| cluster_post_nodes_view | 10.10.0.1:9312,10.10.0.1:9320:replication,10.10.1.1:9312,10.10.1.1:9320:replication |