Detach Indexes from the Replication Process

Indexes are usually divided into slices. You can define which slices to replicate on each host when defining host roles. For more information, see Configure Roles in the Exalead CloudView Installation Guide.

When index generation is complete on the primary server side, secondary servers receive the information that a new index generation is available.

secondary servers download new index files using a proprietary binary file transfer protocol.

For maintenance or operation purposes, you may need to stop the replication process that is, detach replicas from the primary server.

1. Index replica on secondary server 1 has been detached from the primary server:
   • Modifications made to the primary server index are not replicated anymore.
   • Index replica on secondary server 1 is still available to process search queries.
2. Once modifications have been performed and the index has been reattached, the latest index generation available on the primary server are replicated on secondary server 1.

1. If you need to make changes to the configuration (for example, search logic), detach the secondary server from the primary server:

   ./cvinit.[sh|bat] detach

2. Go to the API Console: http://<HOSTNAME>:<BASEPORT+1>/api-ui .
3. Click Manage to display the Management services.
4. To detach the index slice from the replication:
   • Select MAMI indexing .
   • Under Operation, select the detachSliceReplica method.

     <DetachSliceReplica xmlns="exa:com.exalead.mercury.mami.indexing.v10"
                   BuildGroup="bg0" indexSlice="0" sliceInstance="i1" />

5. Click Save.

The replication pauses but the indexing process continues. Alternatively, you can detach the index slice by clicking Detach in Home > Indexing > Replication.