You can remove a backup host from a distributed system. You may want to do this if you used the host for test purposes and no longer need it in the distributed system.
If you remove this host, TREX automatically removes these assignments. The affected indexes then no longer have a backup index server. If you want indexing to be highly available, you need to assign these indexes to another backup index server.
This is displayed in the column using the entry +backup. You should not remove the host if the backup index server is active. If you remove the host anyway, the system does not switch automatically to using the master index server. The master index server is only assigned to the affected indexes when it is next started.
If this is the case, you have to assign another master index server to the indexes before removing the host.
If you remove the host, TREX removes these assignments automatically. You have to assign these indexes to another slave index server too.
See also:Changing Index Assignments
See also:Changing Queue Assignments
The TREX instance is still installed on the removed backup host. The host may still contain configuration data with information on the distributed system. However, since these configuration files are not consistent, the TREX instance on this host will normally not start any longer. You should therefore deinstall this TREX instance.