Skip to content

FATAL no writing but write callback called - TcpConnectionImpl.cc:328  #311

Closed
@prm-james-hill

Description

@prm-james-hill

I’m using Drogon’s HttpClient but figured it would make more sense to put this here:

  • Using v1.9.1 of Drogon and v1.5.15 of Trantor.
  • It’s in an AWS environment that I can’t easily modify or put more verbose logging on. I’ve been unsuccessful in getting any kind of repro in a simpler environment.
  • Not sure how to quantify it but I guess pretty infrequent. This env has ~50 TCP connections (as far as HttpClient is concerned) and this gets logged once every ~5,000,000 requests.
  • Load on the server - and the client in particular - doesn’t seem to matter. It seems to happen specifically when the network is unstable.
    • If a sendRequest() fails with “Timeout” status then there’s no log.
    • If a sendRequest() fails with “Network failure” status then this log sometimes accompanies it.

I realize it’s a high ask to fix this under these conditions. I’m more curious if it’s safe to ignore this and if we can downgrade the log severity. I haven’t noticed any kind of memory corruption (though haven't actually had it happen under ASan) or resource exhaustion accompanying it.

(I also noticed this change from a couple hours ago. If that’s likely relevant I’m happy to upgrade and report back when it’s released.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions