Extending index search timeout for TIBCO LogLogic LMI
Article ID: KB0077315
Updated On:
| Products | Versions |
|---|---|
| TIBCO LogLogic Log Management Intelligence | all versions |
Description
The index search feature uses a default timeout value of 300 seconds, or 5 minutes. This is inadequate for larger time frames on appliances that have higher rates of ingestion. Although splitting the search into smaller searches can work around this it is not ideal. The procedure below can be used to modify the index search timeout.
Issue/Introduction
This article explains how to extend the index search timeout value for LMI appliances.
Resolution
On LMI appliances prior to version 5.5.0:
1. Login to the shell as “toor”.
2. Open the /loglogic/tomcat/webapps/logapp20/WEB-INF/web.xml file.
3. Change the "fulltextSearchTimeout" param-value from 300 to the desired timeout, in seconds.
4. Save your changes.
5. Restart the engine_tomcat service to apply the changes:
$ mtask -s engine_tomcat restart
Note the timeout value may need adjusted multiple times depending on user search criteria before finding a value that is sufficient. Although an LMI administrator can just simply specify a very high value the first time to avoid multiple changes this would allow users to execute searches that could run for days and consume appliance resources.
Starting in LMI 5.5.0 the index search timeout value was moved to be stored in a database table rather than in the web.xml file. This eliminates the need to restart Tomcat to apply changes. It also allows easier modification by exposing the value in the GUI.
On LMI appliances prior to version 5.5.0:
1. Login to the web GUI.
2. Click on Administration Settings.
3. Scroll down to the Index Search Settings section.
4. Change the value then click Update. Note that in the GUI this setting is measured in minutes.
Note that this timeout value does not affect the advanced search that was introduced in LMI 6.1.0 even though advanced search still utilizes index data for the data set that is searched.
Note that for summary index searches a separate timeout value is used. This timeout value is controlled by the aggregatedIndexSearchTimeout parameter in the same web.xml file mentioned above and regardless of which LMI version is used.
1. Login to the shell as “toor”.
2. Open the /loglogic/tomcat/webapps/logapp20/WEB-INF/web.xml file.
3. Change the "fulltextSearchTimeout" param-value from 300 to the desired timeout, in seconds.
4. Save your changes.
5. Restart the engine_tomcat service to apply the changes:
$ mtask -s engine_tomcat restart
Note the timeout value may need adjusted multiple times depending on user search criteria before finding a value that is sufficient. Although an LMI administrator can just simply specify a very high value the first time to avoid multiple changes this would allow users to execute searches that could run for days and consume appliance resources.
Starting in LMI 5.5.0 the index search timeout value was moved to be stored in a database table rather than in the web.xml file. This eliminates the need to restart Tomcat to apply changes. It also allows easier modification by exposing the value in the GUI.
On LMI appliances prior to version 5.5.0:
1. Login to the web GUI.
2. Click on Administration Settings.
3. Scroll down to the Index Search Settings section.
4. Change the value then click Update. Note that in the GUI this setting is measured in minutes.
Note that this timeout value does not affect the advanced search that was introduced in LMI 6.1.0 even though advanced search still utilizes index data for the data set that is searched.
Note that for summary index searches a separate timeout value is used. This timeout value is controlled by the aggregatedIndexSearchTimeout parameter in the same web.xml file mentioned above and regardless of which LMI version is used.
Feedback
Yes
No
Powered by
