Distributed File Polling
| Mule Runtime Engine versions 3.5, 3.6, and 3.7 reached End of Life on or before January 25, 2020. For more information, contact your Customer Success Manager to determine how you can migrate to the latest Mule version. |
Enterprise Edition
Some endpoints, such as the File Endpoint or FTP Endpoint, regularly poll directories and read certain files as they are created in the directories polled. These files may reside on a remote file system, including file systems of nodes belonging to a Mule High Availability (HA) Cluster.
Up to Mule 3.3.x, all file poll requests sent to a cluster were channeled through a single node in that cluster. This ensured file consistency by avoiding the possibility of file system sync issues, but had the disadvantage of introducing a bottleneck, reducing the performance of the cluster.
Mule 3.4 introduces file polling for clusters' distributed file systems, which makes it possible to poll files in all cluster nodes. Enabled by default, this feature is used by the following endpoints:
Requirement
To use distributed file polling, the flow’s Processing Strategy must be synchronous. If the processing strategy is asynchronous, Mule will automatically disable distributed file polling, and revert to the old behavior.
|
You can create and configure clusters with the graphical interface available in the Mule Management Console, or manually by editing the cluster configuration file. For additional configuration options, including cluster network parameters, see Creating and Managing a Cluster Manually. |