Shared File System Failure

It is recommended that you use an external file system to store files created by the application, for instance mlXML documents, log files, and so on.

The external file system should be placed onto a fast, reliable disk array and should ideally be on a different machine from the database for better performance.

Conditions such as a full file system and wrong permissions could lead to an effective component failure. The impact of temporary network outages is particularly severe for the external file system. In most cases a DNS mapping has to be performed before the external file system can be accessed, adding one more component which can fail.

Failure can occur if the Application server is no longer able to access the file system on which the cluster shared information is located. This typically happens during any of the file operations:

  • File system existence check
  • File Read/Write operations
  • Getting the file name from the file system