When you reindex from scratch on a clustered HCL Connections deployment, reindexing takes
place in the background while the system continues to service requests
of the existing index. When reindexing completes, you then switch
to the new index. The update process includes ripple restart of Search
nodes.
Before you begin
To use administrative commands, you must use the wsadmin client.
See Starting the wsadmin
client for information about how to start the wsadmin client. This
procedure uses the following three-node cluster as an example:
Procedure
- Verify that you have root permissions for all three servers.
- Use the following commands to verify that both search nodes
have enough free disk space for seedlist files and a new index. You
need at least three times the size of the current index:
:df -kh
du -ksh /local/IBM/LotusConnections/data/local/search/index
- Create a placeholder for the new index on node1, complete
the following steps:
- SSH to search node1 and switch to root user.
- Create empty directories for the background crawling
and indexing functions:
mkdir --parents /local/tmp/index.2014.Apr.06
cd /local/tmp/index.2014.Apr.06
mkdir ./backgroundCrawl ./backgroundFileExtraction ./backgroundIndex
- Start to index on node1, complete the following steps:
- SSH to the deployment manager node and switch to root
user.
- Start wsadmin, enter the following commands:
cd /local/IBM/WebSphere8/AppServer/profiles/Dmgr01/bin
./wsadmin.sh -lang jython
execfile("searchAdmin.py")
- Start background indexing and crawling of all configured
services, enter the following command:
SearchService.startBackgroundIndex("/local/tmp/index.2014.Apr.06/ backgroundCrawl ",
"/local/tmp/index.2014.Apr.06/ backgroundFileExtraction ", "/local/tmp/index.2014.Apr.06/
backgroundIndex ", "all_configured")
- Monitor and verify that indexing completes on node1, complete
the following steps:
- SSH to search node1 and switch to root user.
- Monitor progress on node1's SystemOut.log for
any warning or error messages.
Example:
.CLFRW0577I: Search has started background crawling and indexing.
Index will be built in /local/tmp/index.2014.Apr.06/backgroundIndex.
- When the process completes correctly, the following
marker file is created: /local/tmp/index.2014.Apr.06/ backgroundIndex/INDEX.READY
- Copy the new index to node2, complete the following steps:
- SSH to search node2 and switch to root user.
- Enter the following commands:
mkdir /local/tmp/index.2014.Apr.06
scp -r root@icappnode1:/local/tmp/index.2014.Apr.06/backgroundIndex /local/tmp/index.2014.Apr.06/
Note: This
step does not replace the active index.
- Prepare to replace the active index, complete the following
steps on the deployment manager node:
- Record all enabled indexing tasks, enter the following
command:
SearchService.listTasks()
- Disable all enabled indexing tasks, enter the following
command for each enabled task:
SearchService.disableTask("taskname")
- Verify that no tasks are still running. You should get
an empty output from the following command:
SearchService.listRunningTasks()
- Replace the active index on node1, complete the following
steps:
- Stop WebSphere® Application
Server on Search node1.
- Move the original index out of active position, enter
the following command:
mv /local/IBM/LotusConnections/data/local/search/index/*
/local/IBM/LotusConnections/data/local/search/index.previous
- Move the new index into active position, enter the following
command:
mv /local/tmp/index.2014.Apr.06/backgroundIndex/*
/local/IBM/LotusConnections/data/local/search/index
- Start WebSphere® Application
Server on Search node1.
- Replace the active index on node2, complete the following
steps:
- Stop WebSphere® Application
Server on Search node2.
- Move the original index out of active position, enter
the following command:
mv /local/IBM/LotusConnections/data/local/search/index/*
/local/IBM/LotusConnections/data/local/search/index.previous
- Move the new index into active position, enter the following
command:
mv /local/tmp/index.2014.Apr.06/backgroundIndex/*
/local/IBM/LotusConnections/data/local/search/index
- Start WebSphere® Application
Server on Search node2.
- Resume indexing over the new index, take the following
steps:
- On the deployment manager node, close and reopen wsadmin.
Enter the following commands:
cd /local/IBM/WebSphere8/AppServer/profiles/Dmgr01/bin
./wsadmin.sh -lang jython
execfile("searchAdmin.py")
- Purge all traces of the previous index from the database,
enter the following command:
SearchService.notifyRestore("true")
- Enable all tasks, for each task you previously disabled,
enter the following command:
SearchService.enableTask("taskname");