-
Notifications
You must be signed in to change notification settings - Fork 712
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scope doesn't see connections between the pyapp and goapp in the example #111
Comments
|
yes; it goes:
because... |
I've seen it connect occasionally, which leads me to think its that the requests are just too quick. |
Did you try tweaking the -probe.spy.interval? edit: I'm surprised the Python requests module doesn't maintain KeepAlive connections... |
Yes even then its intermitted. As far as I can tell the connections are kept alive... |
Interestingly I also see the python client talking to the scope probe sometimes, which I pretty sure can't happen... |
So there are no incoming connections to the goapp in proc:
23F0 = 9200, the elastic search port |
But the connections do appear in the python add:
|
So no inode associate with those connections |
and the state 06 is TIME_WAIT |
So yeah, no keep alive... |
And its the python end
|
python requests does keep alive within a session.... FFS |
I'm thinking this is because http keep alive isn't being honoured or something. But connections are definitely going through.
The text was updated successfully, but these errors were encountered: