Open topic with navigation
The Distributed Action Handler distributes actions between child servers. It also performs some additional processing on actions. For example, in mirror mode it can apply templates, and recognize and distribute administrative actions to all child servers.
Depending on your system, you can use Distributed Action Handler modes to reduce the amount of additional processing that Distributed Action Handler performs, which can improve the performance of the system.
In fast mirror mode, Distributed Action Handler distributes actions between mirrored child servers but does not perform any additional processing to actions. You can use this option to increase the performance of your IDOL system in mirror mode when you use Distributed Action Handler only for requesting information from child servers.
When running the Distributed Action Handler in fast mirror mode:
You cannot send state-changing actions to the Distributed Action Handler (for example, actions including the
StoreState action parameters).
You cannot request additional processing on actions (for example, actions that use the
Output action parameters).
You cannot use document IDs in action parameters.
You cannot use distributed actions (actions to send to all child servers) or asynchronous actions.
In simple combinator mode, Distributed Action Handler does not use virtual databases to distribute and combine actions in non-mirror mode. Distributed Action Handler forwards the
DatabaseMatch action parameter to child servers, and combines results from all child servers.
This option reduces the amount of processing that Distributed Action Handler must perform to distribute and combine virtual database.