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

i/o failure #5158

Closed
HudiDev opened this issue Oct 31, 2018 · 5 comments
Closed

i/o failure #5158

HudiDev opened this issue Oct 31, 2018 · 5 comments

Comments

@HudiDev
Copy link

HudiDev commented Oct 31, 2018

I am using parse server as a BAAS for my android app.
Everything Is working like a charm, except, when I use the app intensely I.E. if I send several requests in a very small span of time (refreshing the data many times quickly) from my android client to the parse server, the server freezes. and I get a message back from my cloud function saying: "i/o failure".

I am not getting any info in my parse.logs file related to the issue besides the "i/o failure" message on client-side
I would be more then happy to understand the cause for this issue. and I how to resolve it.

Environment Setup

  • Server

    • parse-server version: 1.17.3
    • Operating System: Ubuntu (Bitnami image)
    • Localhost or remote server? AWS
  • Database

    • MongoDB version: v3.0.9
    • Localhost or remote server? Localhost
@flovilmart
Copy link
Contributor

This means you are saturating your server, you should scale it up, increase it’s capacity or number of instances.

Overall it’s not relate particularly to this project, but any nodejs based program can face this issue. Server fault would be the best place for you to get accurate help.

@HudiDev
Copy link
Author

HudiDev commented Oct 31, 2018

The weird part is that It happens even with a single user traffic, meaning even if at this moment currently there is only a single user sending requests intensely, it will still crash, does that make any sense?

@JacobJT
Copy link

JacobJT commented Oct 31, 2018

Link me to your server fault post and I'll answer there, but they like to keep these issues about problems with the repo / source code, not problems with your implementation.

@HudiDev
Copy link
Author

HudiDev commented Oct 31, 2018

got it 👍

@HudiDev
Copy link
Author

HudiDev commented Oct 31, 2018

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