chore: only output log in debug when we cannot get next message

topfreegames / pitaya

Scalable game server framework with clustering support and client libraries for iOS, Android, Unity and others through the C SDK.

MIT License

2.38k stars 480 forks source link

chore: only output log in debug when we cannot get next message #416

Closed kalabiyau closed 3 months ago

kalabiyau commented 3 months ago

The following we observe in production:

Error reading next available message: read tcp 192.168.1.1:3250->192.168.1.2:34184: read: connection reset by peer

These connections are part of the TCP health-checks which AWS LB does. Healthcheck succeed as it can establish a connection successfully, but pitaya would produce this error log. It might be useful to find such cases but in higher log level - e.g. Debug

kalabiyau commented 3 months ago

superseded by https://github.com/topfreegames/pitaya/pull/417