Configuring the NFS mount point for use as a staging area

Content Platform Engine has a staging area that is used to store document content as part of ingesting new documents or when moving documents from one storage location to a different storage location. This staging area can be configured with an NFS mount point. Configure the mount point to prevent loss of data when your disk volume is at full or near full capacity.

About this task

When a disk volume is full or near its full capacity, the NFS server or client might return success to Content Platform Engine for a write operation. However, due to the asynchronous or write cache feature of the NFS server and client, the object's content might not be completely written to the disk volume. In this condition, Content Platform Engine does not receive an error from NFS that the content was not written to the disk and when Content Platform Engine requests the object size, the NFS server returns the proper size of the object, as if it was completely and properly stored in the disk volume. Since there was no error returned from NFS when the Content Platform Engine write operation finished, it appears to Content Platform Engine that the write operation completed successfully.

You can prevent this condition by configuring your NFS mount point correctly.

Procedure

To configure the NFS mount point:

Check your OS-dependent NFS server options and NFS client mount command options and disable any asynchronous write, or write-back cache feature of the NFS client or server.
For example, the noac option disables file attribute caching.

Results

Note that when you disable the asynchronous write or write back cache feature of the NFS, the performance can decrease. Monitor your NFS-mounted disk volumes and ensure that your disk volumes are not near their full capacity. Before a disk volume becomes near its full capacity, expand the NFS-mounted disk volume to ensure that you have adequate free disk space available for your storage.