The Reactionner daemon is in charge of notifications and launching event_handlers. There can be more than one Reactionner.
Variables in red are required, while those in black are optional. However, you need to supply at least one optional variable in each definition for it to be of much use.
||dns name of ip address
# Optional parameters
manage_sub_realms 0 ; Does it take jobs from schedulers of sub-Realms?
min_workers 1 ; Starts with N processes (0 = 1 per CPU)
max_workers 15 ; No more than N processes (0 = 1 per CPU)
polling_interval 1 ; Get jobs from schedulers each 1 second
timeout 3 ; Ping timeout
data_timeout 120 ; Data send timeout
max_check_attempts 3 ; If ping fails N or more, then the node is dead
check_interval 60 ; Ping node every minutes
- This variable is used to identify the short name of the reactionner which the data is associated with.
- This directive is used to define the address from where the main arbier can reach this reactionner. This can be a DNS name or a IP address.
- This directive is used to define the TCP port used bu the daemon. The default value is 7772.
- This variable is used to define if the reactionner must be managed as a spare one (will take the conf only if a master failed). The default value is 0 (master).
- This variable is used to define the realm where the reactionner will be put. If none is selected, it will be assigned to the default one.
- This variable is used to define if the poller will take jobs from scheduler from the sub-realms of it’s realm. The default value is 1.
- This variable is used to define all modules that the reactionner will load.
- This variable is used to define the checks the reactionner can take. If no reactionner_tags is defined, reactionner will take all untagued notifications and event handlers. If at least one tag is defined, it will take only the checks that are also taggued like it.
By default, there is no reactionner_tag, so reactionner can take all untagued notification/event handlers (default).