-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TCP timeout issue #401
Comments
Hello Yuda Tian, the variables you mention control timeouts on inbound connections, and are thus unrelated. |
Right, I'm trying to discard the metrics from instrumentation (by sending it to a reserved IP for discarding), I think it's referenced here: AFAIK there doesn't seem to be any support for this yet? |
that's correct. the simple solution is to simply send the stats back into the relay, which is very handy anyway. |
So I would be setting: |
yep |
as this was a config issue, i'll consider this resolved. |
[Logs]:
As you can see above, there exists a recurring timeout (exactly every 2m).
I thought this would be related to issue#250 and PR#318, so I changed this carbon-relay-ng.ini files
plain_read_timeout
andpickle_read_timeout
to "0s".However, I still get the TCP timeout error.
Is this regular behavior (aka every single connection creates a new socket and each socket automatically times out after 2m)? Otherwise, looking for advice on how to fix this.
The text was updated successfully, but these errors were encountered: