You can monitor PCH counters to determine if the content
cache queue is growing and whether there are files in the inbound
directory that are being marked as invalid. If needed, consider tuning
four parameters in the FileNet.properties file
to control processing of the inbound file directory for the content
cache.
Monitor the following PCH counters:
- Cache Inbound Mover Queue Entries - This counter provides the
number of items in the remote cache inbound directory in the queue
to be moved.
- Cache Invalid Element Queue Entries - This counter provides the
number of items that were not moved out of the inbound directory before
the file was considered abandoned.
If needed consider tuning the following
FileNet.properties file
parameters:
- Content.CacheAbandonCleanupAgeSeconds - This is the time allotted
for a file in the inbound directory to be renamed before the file
is considered abandoned and removed. The default value is 30 minutes.
- Content.CacheInboundMoverTasks - This is the number of threads
allotted to process files in the inbound directory. The default is
5.
- Content.CacheInvalidElementTasks - This is the number of threads
allotted to process files in the inbound directory marked as abandon.
The default is 1.
- Content.CacheInvalidElementTasks - This is the number of threads
to process files in the inbound directory marked as abandon. The
default is 1.
The method you use to tune these parameters
depend on your type of WAN conditions. You should monitor the new
PCH counters to see if the queue is growing and not stabilizing and
if there are files in the inbound directory that are being marked
as invalid. If either of these conditions occur then they should
experiment with increasing the inbound mover tasks or the abandon
cleanup time or both. Increasing the number of inbound mover tasks
provides more threads to process the inbound directory while increasing
the abandon cleanup time extends the time that a file is marked as
abandoned.