Before you begin
You must remove the node from the cluster before using the SearchService.removeIndexingNode command to remove it from the index management table. For information about how to remove nodes, see Removing nodes from a cluster
To use the SearchService.removeIndexingNode command, you must use the IBM
® Application Server wsadmin client. See Starting the wsadmin client
About this task
You can use the removeIndexNode command to remove an entry from the SR_INDEX_MANAGEMENT table that is added or updated by Search servers at start-up time.
To remove a node from the index management table, complete the following steps.
Parent topic: Managing the Search index
Removing nodes from a cluster
Listing indexing nodes
- Start the wsadmin client from the following directory of the system on which you installed the Deployment Manager:
is the WebSphere
Application Server installation directory and dm_profile_root
is the Deployment Manager profile directory, typically dmgr01.
You must start the client from this directory or subsequent commands that you enter do not execute correctly.
- After the wsadmin command environment has initialized, enter the following command to initialize the Search environment and start the Search script interpreter:
If prompted to specify a service to connect to, type 1 to pick the first node in the list. Most commands can run on any node. If the command writes or reads information to or from a file using a local file path, you must pick the node where the file is stored.
When the command is run successfully, the following message displays:
Search Administration initialized
- Use the following command:
Removes the specified node from the index management table.
This command takes a single argument:
- nodeName. The name of the node to be removed. This argument is a string value that takes the following format:
- To retrieve a list of the indexing nodes in your deployment, run the SearchService.listIndexingNodes() command. For more information, see Listing indexing nodes.
When the command runs successfully, 1 is printed to the wsadmin console. If the command does not run successfully, 0 is printed to the wsadmin console.