-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Parse Server on Heroku logs many "H28 Client Connection Idle" warnings #1307
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
Comments
Cause seemed to be a performance issue. Upscaled the dynos in Heroku and reduced the number of H28s. |
Hi @mtrezza, we're seeing this too and wondered if you had any more insights to share. |
Hi @alexblack, I can't remember anymore but I'd first check cloud code, maybe even remove cloud code and see if you still have these errors. |
Hey @mtrezza — any chance you can elaborate? We see a lot of these as well, do you mean that the quantity of Cloud Code functions you have is causing issues? Or just disabling it altogether? |
@woodardj it seemed to be a Heroku performance related issue. Upscaling the dynos in Heroku reduced the number of H28s. |
With Parse Server deployed on Heroku I see quite a few warnings from the Heroku router:
H28 Client Connection Idle
. The server is the API endpoint for an iOS app.According to Heroku docs this warning occurs when:
Can this possibly be an issue with the Parse iOS SDK?
Has anyone else experienced this?
Update:
I was able to track this down to a single request type to a specific class. So I guess this is just something in the app logic. I will further investigate this and update here.
The text was updated successfully, but these errors were encountered: