-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
"Send failed" error more than once per second #1817
Comments
tendermint/go-amino’s aminoscan tool now lets you type --concrete-name as an option…
So those are HasVote messages… it’s expected to fail often, because HasVote messages are sent opportunistically. mconnection.Send() returns false… the caller should log an Error if it wants to, instead of logging it from mconnection.Send(), imo. Or it could be Info/Debug level logging so it doesn’t clog up output. I propose that we turn the "Send failed ..." log messages to Info. |
Another note: We really shouldn't be creating new goroutines for every send in Broadcast for things like this... I don't know if there's an existing issue to refactor Broadcast to be more mindful of goroutine resource consumption (it's not like a Service or peer connection where there are some limited number of them; Broadcast gets called N times where N can be large), but another option may be to implement BroadcastTry and call TrySend instead, not in separate go-routines, and see if we can migrate each Broadcast calls to BroadcastTry call. |
There is: #805 |
Changed log level to debug in #2857 |
Awesome !!! 🍺 |
…endermint#1808) (tendermint#1817) (cherry picked from commit 149ac1e) Co-authored-by: Sergio Mena <sergio@informal.systems>
This error is spamming the logs.
While grepping my logs, I found this error :
Using
0.19.0-c671181
onUbuntu 16.04
+go version go1.10 linux/amd64
The text was updated successfully, but these errors were encountered: