我看到了其中的一些。我理解他们的意思,这就是为什么我无法理解为什么会这样。非常不一致,并且似乎不是超时问题。
相关内容:
一些日志数据:
Oct 29 18:22:12 myapp-web-production heroku / router:sock = client at = error code = H18 desc =“Request Interrupted”method = GET path =“/ aroute”host = ... request_id = ... fwd =“##。##。##。###”dyno = web.1 connect = 2ms service = 34ms status = 503 bytes = 3816
Oct 29 18:22:13 myapp-web-production heroku / router:sock = client at = error code = H18 desc =“Request Interrupted”method = GET path =“/ aroute”host = ... request_id = ... fwd =“##。##。##。###”dyno = web.1 connect = 1ms service = 538ms status = 503 bytes = 3822
Oct 29 18:22:14 myapp-web-production heroku / router:sock = client at = error code = H18 desc =“Request Interrupted”method = GET path =“/ aroute”host = ... request_id = ... fwd =“##。##。##。###”dyno = web.1 connect = 1ms service = 406ms status = 503 bytes = 13927
我被困住了。任何帮助将不胜感激。
答案 0 :(得分:6)
我认为sock=client
属性意味着客户端只是在服务器响应之前断开连接。我们可以通过向处理程序添加一个人为的10s延迟来重现这一点,然后,例如,在Web浏览器中请求端点并在服务器响应之前关闭它。
我们只是从日志中过滤掉sock=client
的所有H18。