Skip to content
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

Parse Server on Heroku logs many "H28 Client Connection Idle" warnings #1307

Closed
mtrezza opened this issue Mar 31, 2016 · 5 comments
Closed

Comments

@mtrezza
Copy link
Member

mtrezza commented Mar 31, 2016

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:

The client did not send a full request and was terminated due to 55 seconds of inactivity. For example, the client indicated a Content-Length of 50 bytes which were not sent in time.

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.

@mtrezza
Copy link
Member Author

mtrezza commented Mar 31, 2016

Cause seemed to be a performance issue. Upscaled the dynos in Heroku and reduced the number of H28s.

@mtrezza mtrezza closed this as completed Mar 31, 2016
@alexblack
Copy link

Hi @mtrezza, we're seeing this too and wondered if you had any more insights to share.

@mtrezza
Copy link
Member Author

mtrezza commented Nov 16, 2016

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.

@woodardj
Copy link

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?

@mtrezza
Copy link
Member Author

mtrezza commented Nov 13, 2017

@woodardj it seemed to be a Heroku performance related issue. Upscaling the dynos in Heroku reduced the number of H28s.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants