We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Under load the healthcheck endpoint in the public application that connects to the staff API Excon produces 502 errors.
The excon gem upgrade is a possible cause, upgraded from 0.49.0 to 0.54.0 in a commit that was part of the breaking change 11e95fe.
Currently the problem is mitigated by not resusing the excon connection to the API, adding 'persistent: false' to the call o(see commit f7450b3)
Note that the 'head' call to excon seems to be the problematic one and using 'get' is not affected.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Under load the healthcheck endpoint in the public application that connects to the staff API Excon produces 502 errors.
The excon gem upgrade is a possible cause, upgraded from 0.49.0 to 0.54.0 in a commit that was part of the breaking change 11e95fe.
Currently the problem is mitigated by not resusing the excon connection to the API, adding 'persistent: false' to the call o(see commit f7450b3)
Note that the 'head' call to excon seems to be the problematic one and using 'get' is not affected.
The text was updated successfully, but these errors were encountered: