Radiator Server Documentation — v10.34.2
Retrying Diameter request at an alternate peer
A Diameter request answered with 3002 or 3004 is sent once more to another peer-group member.
Emission
Log level: TRACE
Per-request tracing: No
Logged when a peer answers a forwarded request or a Diameter backend request
with DIAMETER_UNABLE_TO_DELIVER (3002) or DIAMETER_TOO_BUSY (3004) and
Radiator Server sends the same request once more to another eligible member of
the peer group. diameter_upstream_peer answered with diameter_result_code,
and diameter_alternate_peer receives the retry. When no other member is
eligible, or the deadline has passed, the first answer is returned instead.
No action. If retries are frequent, check the load and drain state of the answering peer.