MR::peer¶
Description¶
The MR::peer command defines a peer to use for routing a message to.
The peer may either refer to a named pool or a tuple (IP address, port
and route domain iD). When creating a connection to a peer, the
parameters of either a virtual server or a transport config object
will be used. The peer object will only exist in the current
connections connflow. When adding a route (via MR::route add), it will
first look for a locally created peer object then for a peer object
from the configuration. Once the current connection closes, the local
peer object will go away.
Syntax¶
MR::peer <name> [virtual <virtual_name>]
[connection-mode <per-peer | per-blade | per-tmm | per-client>]
[max-connections <nonnegative_integer>]
[pool <pool name>]
[host <host tuple>]
MR::peer <name> [config <transport_config_name>]
[connection-mode <per-peer | per-blade | per-tmm | per-client>]
[max-connections <nonnegative_integer>]
[pool <pool name>]
[host <host tuple>]
[ratio <ratio-value>]
Note: ratio keyword is only available in v13+, and
connection-mode/max-connection keywords only available in v13.1+
Examples¶
when CLIENT_ACCEPTED {
MR::peer self_peer config tc1 host "[IP::remote_addr]:[TCP::remote_port]"
GENERICMESSAGE::route add dest "[IP::remote_addr]" peer self_peer
}