system:completed_requests at times reports wrong status

Requests eligible to be stored in completed_requests log may end up being logged with the wrong state if the client application has closed the connection.
Although the symptom is cosmetic (state is completed vs closed) - the underlying issue is more serious, in that, because of a race condition, the closeNotify goroutine may get to execute after the request has completed, and that may lead to undesired effects such as trying to write to closed channels, etc.