Setting the Asynchronous Actions module parameters
The asynchronous actions module allows to call asynchronous actions used for inter-agent communication to recover information, such as the operational rule status or the latest identity upload. This module propagates XML/RPC calls through the BCM topology instead of transferring files. It is multithreaded, but will never wait for threads. It also memorizes all information, to save the database read times It however maintains a database, to be able to recover its status and pending actions in case of an agent stop or crash.
Parameter | Default Value | Description |
---|---|---|
Number of threads | 5 | Enter the number of threads to use for asynchronous calls |
Retry Delay (Priority 0) | 300 | Enter the retry interval for calls of priority 0 in seconds (highest priority, currently not in use) |
Retry Delay (Priority 1) | 300 | Enter the retry interval for calls of priority 1 in seconds (used for operational rule status and identity uploads) |
Retry Delay (Priority 2) | 300 | Enter the retry interval for calls of priority 2 in seconds (used for operational rule assignments) |
Retry Delay (Priority 3) | 300 | Enter the retry interval for calls of priority 3 in seconds (currently not in use) |
Retry Delay (Priority 4) | 300 | Enter the retry interval for calls of priority 4 in seconds (lowest priority, currently not in use) |
Prefer IP Addresses | Yes | Defines whether the identification for communication between the agents and with the master is effected via the agents' IP addresses or over their host names. This is to facilitate networking in environments that do not have DNS name resolution in place. |
Object Time to Live (sec) | 300 | In order to prevent non-transferable data from remaining eternally in the queue, each object is assigned a specific time in seconds that it may stay in the queue and wait to be passed on its way to its destination. |
Min Purge Delta Time (sec) | 10 | The minimum interval (in seconds) between two cleanup operations of the asynchronous actions database of all actions called since the last purge. |
Maximum Action Count | 100000 | The maximum number of actions that can be stored. The module refuses all incoming remote actions until the number of stored actions drops below this value. |
Maximum File Count | 100000 | The maximum number of files that can be stored. The module refuses all incoming remote files until the number of stored files drops below this value. |
Comments
Log in or register to comment.