Cribl TCP > Cribl TCP - Destination side getting a “message:sender state change” with a “stage: STAL
Hi, Using Cribl TCP > Cribl TCP and on the destination side getting a “message:sender state change” with a “stage: STALE”. Also seeing messages of “reason: marked as stale”.
What is causing this and is this something to be concerned about ?
Found this digging around as on the Cribl TCP destination we are seeing the “Blocked status” on the charts tab showing as 1 however all servers are green under the status. The final destination is also Green and we cannot find any reason why the Blocked status is enabled.
Original message in Cribl Community Slack Message: https://cribl-community.slack.com/archives/CPYBPK65V/p1683177474390609
Best Answer
-
It's not necessarily a problem. Stale senders are those where a connection was made at one point in this destination, but something like configuration change, DNS changes, rebalancing, etc. have made the destination no longer need to send to that IP address.
If you're seeing it happen repeatedly, and seems to match the same interval as DNS resolution period (seconds) advanced setting, check your Max connections setting (also in Advanced Settings). This stale sender message will also happen if more IP addresses are resolved from the endpoints you have configured than you've allowed concurrent senders.
1
Answers
-
It's not necessarily a problem. Stale senders are those where a connection was made at one point in this destination, but something like configuration change, DNS changes, rebalancing, etc. have made the destination no longer need to send to that IP address.
If you're seeing it happen repeatedly, and seems to match the same interval as DNS resolution period (seconds) advanced setting, check your Max connections setting (also in Advanced Settings). This stale sender message will also happen if more IP addresses are resolved from the endpoints you have configured than you've allowed concurrent senders.
1