Avoiding unnecessary full search crawls
Use an administrative command to avoid performance hits by avoiding unnecessary full search crawls.
About this task
HCL Connections keeps records of deleted files. The seedlistSettings.maximumIncrementalQuerySpanInDays property in the LotusConnections-config.xml configuration file specifies the number of days for which these records are saved before they are deleted. The records can be deleted by the SearchClearDeletionHistory task after the number of days that are specified by the property.
You can avoid performance hits by making sure that deletion records are kept long enough to be read by the incremental search crawler. The incremental search crawler needs these deletion records to update the Search index. If the records are deleted before the incremental crawler reads them, updates will be incomplete. When the updates are incomplete, HCL Connections performs a full crawl instead of an incremental crawl. Full crawls delete the existing Search index and create a new one, which is more time-consuming than incremental crawls. To avoid frequent full crawls, make sure that the value of the seedlistSettings.maximumIncrementalQuerySpanInDays property is higher than the span of days between incremental crawls. For example, if incremental crawls happen every four days, ensure that the property value is higher than 4. This setting ensures that incremental crawls capture all deletion records. By default the Search crawling task runs every 15 minutes.
Incremental crawls must be left at the default schedule.
Procedure
- Use the wsadmin client to access and check out the HCL Connections configuration files:
- Optional:
If you want to find out the current value of a property, you
can list the current configuration settings and values by using the
following command:LCConfigService.showConfig()
- Enter the following command:
Where number_days is a number greater than or equal to 1 and less than or equal to 30.LCConfigService.updateConfig("seedlistSettings.maximumIncrementalQuerySpanInDays",number_days)
What to do next
Check the configuration files back in during the same wsadmin session in which you checked them out. For more information, see the Applying common configuration property changes topic.