-
Notifications
You must be signed in to change notification settings - Fork 2k
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
connection pooling problem #1544
Labels
type: question
Request for information or clarification. Not an issue.
Comments
@SinanGabel Thanks for reporting the problem. @ace-n Could you have a look at this please. Thanks! |
fhinkel
added
type: question
Request for information or clarification. Not an issue.
and removed
triage me
I really want to be triaged.
labels
Nov 19, 2019
ping @ace-n |
Hi,
Should the example at
https://cloud.google.com/functions/docs/bestpractices/networking be working
now?
Thank you in advance.
Br,
Sinan
…On Tue, 11 Feb 2020 at 19:53, F. Hinkelmann ***@***.***> wrote:
Closed #1544
<#1544>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1544?email_source=notifications&email_token=ABKTZUQZBJTDJMFVOMDTZ3LRCLX2ZA5CNFSM4JOXCVQ2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOWR4HJOA#event-3027793080>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABKTZUQ6RMN6G7GCRX5GRDTRCLX2ZANCNFSM4JOXCVQQ>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I tried your suggestion but it does not work as-is:
(1) http is not allowed.
Likely solution: the port error disappears when using https instead i.e.
const https = require('https');
...
(2) I tried different settings of options to
https.request(options, ...)
but I could not get any to work.For example:
resulted in error message:
Error: getaddrinfo ENOTFOUND https://us-central1-[my_project_id].cloudfunctions.net https://us-central1-[my_project_id].cloudfunctions.net:443
(3) I searched for a solution and found this:
https://github.com/expressjs/express/issues/3556
i.e. not to use your require("https") approach but to simply utilize the expressjs functionality by adding e.g.:(4)
I tried to run artillery with a POST json request that but could not see any gains with and without
req.socket.setKeepAlive({"enable": true})
Here is the artillery .yml I used:
Please advice, thanks :)
The text was updated successfully, but these errors were encountered: