rnewson commented on issue #5495: URL: https://github.com/apache/couchdb/issues/5495#issuecomment-2766078289
Curl can't keep a connection open after it exits (though it can reuse a connection if you pass multiple urls to the curl command `curl localhost:5984 localhost:5984 ...`). nodejs could reuse a connection, assuming you issue multiple requests within the same OS process. That all but a few connections are in TIME_WAIT tells us that one side has closed the majority of connections, and I think it's the client side (curl). We still end up running out of ephemeral ports if the connections aren't closing down promptly. But that is a separate issue from the lack of client-side connection pooling (though we're all clear that that is the common way to mitigate exactly this issue). So... the question is why isn't the CouchDB side cleanly and promptly closing down the connections when curl exits (closing its side)? Are you hitting CouchDB directly here or is :5984 something like haproxy or nginx? If direct, as I've assumed, think we'll need packet traces to figure it out. Also please mention if you are using the default configuration or have made any network-related tweaks in there. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@couchdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
