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.
define reactionner{ | |
reactionner_name | reactionner_name |
address | dns name of ip address |
port | port |
spare | //[0/1]// |
realm | realm name |
manage_sub_realms | [0,1] |
modules | modules |
} |
define reactionner{
reactionner_name Main-reactionner
address node1.mydomain
port 7769
spare 0
realm All
# 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
reactionner_tags tag1
modules module1,module2
}
By default, there is no reactionner_tag, so reactionner can take all untagued notification/event handlers (default).