-
Notifications
You must be signed in to change notification settings - Fork 414
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
keeps reconnect_socket while running wrk command to generate workloads on Linux #283
Comments
Hi, thanks for posting the issues. I am not able to reproduce the error you reported. Would you mind uploading more details about it, such as the error log of the frontend service with
|
Thank you so much for your response and sorry for this late response from me. Yes, I will check the points you mentioned. |
I had a look at the frontend logs with command
It seems that it's a DNS resolution error. So I also checked logs for the jaeger container, and below is the output:
I'm not familiar with docker networking in general, but based on what I found online, it should be dialled up at port 16686, not 16685 right? I tried to use thank you |
Hello all, I've been following the steps listed in README and I'm getting the below problem.
When I run
../wrk2/wrk -D exp -t2 -c100 -d30s -L -s ./wrk2/scripts/hotel-reservation/mixed-workload_type_1.lua http://0.0.0.0:5000/tcp -R2000
inhotelReservation
and any other microservices, I keep gettingreconnect_socket
output to stdout. I added some debug printf statements, and they are fromsocket_writeable
andsocket_readable
function inwrk.c
file.Since the socket is not connected properly, the final output is
Below is a summary of the system I'm running on
Does anyone know how to resolve this?
thanks
The text was updated successfully, but these errors were encountered: