Content Platform Engine uses a temporary folder for extracting the text that is indexed by Content Search Services. To avoid negatively impacting indexing performance, place the temporary folder in a file system that has at least 5 GB of free disk space. Performance can be enhanced if the folder is located on a RAM disk or other fast storage, such as a solid-state drive.
Too little free disk space degrades indexing performance. Content Platform Engine provides a disk checking feature to mitigate the possibility of the text extraction process running out of disk space. Content Platform Engine checks every 600 seconds (10 minutes) that the temporary folder has at least 3 GB of available space. (600 seconds and 3 GB are default values, and can be overridden with Java™ Virtual Machine (JVM) arguments.)
If the available disk space falls below 5 GB (the default minimum of 3 GB plus 2 GB), Content Platform Engine writes a warning to the p8_server_error.log, similar to the following message. However, Content Platform Engine continues to process index requests.
WARN The usable disk space in the xxxx directory used for text extraction is 4,125,562,333 bytes. Dispatching of index requests will be delayed if the available disk space drops below the minimum of 3,221,225,472 bytes required for text extraction.
If the available disk space continues to drop to the point that it is less than the 3 GB minimum, Content Platform Engine holds up dispatching of index requests, plus writes a warning about the hold, similar to the following message. This results in a significant number of index-request retries, degrading indexing performance.
WARN The usable disk space in the xxxx directory used for text extraction is 3,182,442,770 bytes, which is below the minimum of 3,221,225,472 bytes required for text extraction. Dispatching of index requests is delayed until enough disk space is available.
In either case, you will want to free up space on the existing file system, or configure the location of the temporary directory to another local drive.
To improve indexing performance, place the temporary folder in a file system that has double or more of the recommended minimum of 5 GB of available disk space. If the disk-space check determines that available disk space is double or more above the minimum free space setting, the frequency and overhead of disk space checks are reduced, which can improve overall performance.
For example, if there is 10 GB of available disk space and the minimum free space default of 3 GB is used, then the frequency of disk checking is automatically reduced from 600 seconds (10 minutes) to 1200 seconds (20 minutes).
You can determine the performance of the disk space check by enabling summary trace logging of the content-based retrieval subsystem. If the trace is enabled, the Content Platform Engine dispatcher performance data includes the elapsed time (in milliseconds) to perform the disk space check.
With the following Java Virtual Machine (JVM) arguments, you can override the default values that Content Platform Engine uses to check free disk space. In general, however, the checking interval default of 10 minutes and the minimum free disk space default of 3 GB (3221225472 bytes) is adequate in a production environment. (Recall that Content Platform Engine issues a warning if disk space drops below the minimum free disk space setting plus 2 GB. So if the setting is 3 GB, a warning is issued if disk space drops below 5 GB.)
For example, the following JVM setting changes the checking interval to 5 minutes:
-Dcom.filenet.cbr.diskSpaceCheckIntervalInSeconds=300
Setting a value less than or equal to zero disables the low disk space safeguard for text extraction.
For example, the following JVM setting changes the required minimum disk space to 5 GB:
-Dcom.filenet.cbr.minimumDiskSpaceBytes=5368709120
Setting a value less than or equal to zero results in Content Platform Engine logging a warning message and using the default value.