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

continuously post eat all memory and server crash #159

Closed
longhua8800w opened this issue Aug 5, 2020 · 4 comments
Closed

continuously post eat all memory and server crash #159

longhua8800w opened this issue Aug 5, 2020 · 4 comments

Comments

@longhua8800w
Copy link

as descripted above:" all the forked processes keep alive, eat all memory and server crash". this must not be expected, i may run into some low-level stupid mistake. can you provid any clue to solve this?

R version is 3.6 i use RestRserve construct a server to compute a model . if post the url once , it always work well. when i iterate post continuously 。 it always crash when the 40th time 。 error reported is
"WARNING: fork() failed in Rserve_prepare_child(): Cannot allocate memory"

@longhua8800w longhua8800w added bug not-confirmed not-confirmed bugreport labels Aug 5, 2020
@dselivanov
Copy link
Collaborator

Rserve keeps connection open until client closes it. So if your clients don't close connections, worker processes will be alive (as per my understanding time alive is defined by TCP protocol config on your machine) and waiting communication from clients them. See related discussion and suggestions (like putting RestRserve behind proxy which will force connection close or force all clients to share pool of connections) in #25.
I'm closing this ticket. We can continue in #25 if needed.

@dselivanov dselivanov added FAQ Rserve and removed bug not-confirmed not-confirmed bugreport labels Aug 6, 2020
@longhua8800w
Copy link
Author

Thank you for your timely reply ! According to your suggestion, we successfully solved the problem

@dselivanov
Copy link
Collaborator

Thank you for your timely reply ! According to your suggestion, we successfully solved the problem

@longhua8800w what did work for you?

@long-do
Copy link

long-do commented Aug 20, 2020

Hello @longhua8800w ,
Could you share us your solution please? I have the same issue as yours. Thank you.

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

No branches or pull requests

3 participants