If you have implemented a system with master and backup servers and a master server breaks down, the backup server becomes active automatically. When the master server becomes available again, the system swaps back to the master server.
If you create an index while the master server is unavailable, TREX proceeds as follows:
The backup server becomes the master server for this index
This index has no backup server
The TREX admin tool displays this in the Index Landscape area as follows:
TREX does not change this assignment, even when the master server becomes available again. You have to correct the assignment for this index as follows:
Start the TREX admin tool on any host in the distributed system.
Make sure that the master and backup servers are available.
Go to the Index Landscape window.
In the column <light><host_name_master_index_server>:<port>, click on the line for the index in question. Choose Add backup here from the context menu.
Click on the same cell again and choose Switch master/backup from the context menu.
The index now has a backup server, and the master and backup servers are assigned to the index correctly.
Go to the Queue Landscape window.
Carry out the same changes that you just carried out for the index, but this time for the queue.