Manticore Search Manual: Creating a cluster > Setting up replication > Adding and removing an index from a replication cluster

Delete statement removes a cluster specified with name. The cluster gets removed from all the nodes, but its indexes are left intact and become active local non-replicated indexes.

‹›

SQL
HTTP
PHP
Python
javascript
Java

📋

DELETE CLUSTER click_query

POST /sql -d "mode=raw&query=DELETE CLUSTER click_query"

$params = [
    'cluster' => 'click_query',
    'body' => []
];
$response = $client->cluster()->delete($params);

utilsApi.sql('mode=raw&query=DELETE CLUSTER click_query')

res = await utilsApi.sql('mode=raw&query=DELETE CLUSTER click_query');

utilsApi.sql("mode=raw&query=DELETE CLUSTER click_query");

‹›

Response

{u'error': u'', u'total': 0, u'warning': u''}

ALTER CLUSTER <cluster_name> ADD <index_name> adds an existing local index to the cluster. The node which receives the ALTER query sends the index to the other nodes in the cluster. All the local indexes with the same name on the other nodes of the cluster get replaced with the new index.

After the index is replicated, write statements can be performed on any node but index name must be prefixed with the cluster name like INSERT INTO <clusterName>:<indexName>.

‹›

SQL
HTTP
PHP
Python
javascript
Java

📋

ALTER CLUSTER click_query ADD clicks_daily_index

POST /sql -d "mode=raw&query=
ALTER CLUSTER click_query ADD clicks_daily_index
"

$params = [
  'cluster' => 'click_query',
  'body' => [
     'operation' => 'add',
     'index' => 'clicks_daily_index'

  ]
];
$response = $client->cluster()->alter($params);

utilsApi.sql('mode=raw&query=ALTER CLUSTER click_query ADD clicks_daily_index')

res = await utilsApi.sql('mode=raw&query=ALTER CLUSTER click_query ADD clicks_daily_index');

utilsApi.sql("mode=raw&query=ALTER CLUSTER click_query ADD clicks_daily_index");

‹›

Response

{u'error': u'', u'total': 0, u'warning': u''}

ALTER CLUSTER <cluster_name> DROP <index_name> forgets about a local index, i.e., it doesn't remove the index files on the nodes but just makes it an active non-replicated index.

After an index is removed from a cluster, it becomes a 'local' index and write statements must use just the index name as INSERT INTO <indexName>, without the cluster prefix.

‹›

SQL
HTTP
PHP
Python
javascript
Java

📋

ALTER CLUSTER posts DROP weekly_index

POST /sql -d "mode=raw&query=
ALTER CLUSTER posts DROP weekly_index
"

$params = [
  'cluster' => 'posts',
  'body' => [
     'operation' => 'drop',
     'index' => 'weekly_index'

  ]
];
$response = $client->cluster->alter($params);

utilsApi.sql('mode=raw&query=ALTER CLUSTER posts DROP weekly_index')

res = await utilsApi.sql('mode=raw&query=ALTER CLUSTER posts DROP weekly_index');

utilsApi.sql("mode=raw&query=ALTER CLUSTER posts DROP weekly_index");

‹›

Response

{u'error': u'', u'total': 0, u'warning': u''}

ALTER CLUSTER <cluster_name> UPDATE nodes statement updates node lists on each node of the cluster to include every active node in the cluster. See Joining a cluster for more info on node lists.

‹›

SQL
HTTP
PHP
Python
javascript
Java

📋

ALTER CLUSTER posts UPDATE nodes

POST /sql -d "mode=raw&query=
ALTER CLUSTER posts UPDATE nodes
"

$params = [
  'cluster' => 'posts',
  'body' => [
     'operation' => 'update',

  ]
];
$response = $client->cluster()->alter($params);

utilsApi.sql('mode=raw&query=ALTER CLUSTER posts UPDATE nodes')

res = await utilsApi.sql('mode=raw&query=ALTER CLUSTER posts UPDATE nodes');

utilsApi.sql("mode=raw&query=ALTER CLUSTER posts UPDATE nodes");

‹›

Response

{u'error': u'', u'total': 0, u'warning': u''}

For example, when the cluster was initially created, the list of nodes used for rejoining the cluster was 10.10.0.1:9312,10.10.1.1:9312. Since then other nodes joined the cluster and now we have the following active nodes: 10.10.0.1:9312,10.10.1.1:9312,10.15.0.1:9312,10.15.0.3:9312.

But the list of nodes used for rejoining the cluster is still the same. Running the ALTER CLUSTER ... UPDATE nodes copies the list of active nodes to the list of nodes used to rejoin on restart. After this, the list of nodes used on restart includes all the active nodes in the cluster.

Both lists of nodes can be viewed using Cluster status statement (cluster_post_nodes_set and cluster_post_nodes_view).

To remove a node from a replication cluster you need to:

stop the node
remove info about the cluster in <data_dir>/manticore.json (/var/lib/manticore/manticore.json in most cases) on the node you've stopped
run ALTER CLUSTER cluster_name UPDATE nodes on any other node

After this the other nodes will forget about the detached node and the node will forget about the cluster. It won't impact indexes neither in the cluster nor on the detached node.

Deleting a replication cluster

Adding and removing an index from a replication cluster

Managing replication nodes

Removing node from cluster