-
Notifications
You must be signed in to change notification settings - Fork 65
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
'ignoring SIGPIPE signal' under load #121
Comments
Cooperative mode is not the intended mode of operation, because any fatal error terminates the server (since there is only one process which is both the listener and the worker). In the case above, some pipe has been closed while the R process was writing to it so it terminated. |
Thank you very much for answer. Just wanted to clarify one more thing. I'm using Rserve in cooperative mode in order to be able to update the state of the server process time to time (caching some variables to be used during request processing). |
Hi @dselivanov, Sep 19 10:18:34 server_abc Rscript[20367]: Error in (function (..., config.file = "/etc/Rserve.conf") : But the file "/etc/Rserve.conf does not exist on my "server_abc". |
@long-do
As per my understanding one is Rserve which serves via binary protocol and another is Rserve which serves via http.
this is not relevant to RestRserve as all parameters are passed explicitly to
|
I've been trying to debug a problem with disappearing tempdir()s while using RestRserve (see here: rexyai/RestRserve#174 (comment)) and although I can't reliably reproduce it, it seems that when the tempdir() goes missing, I see this error crop up before it.
along with
Is it possible that when this error happens, the R process that is halted takes the |
Hi Simon. Under high-load during benchmarking I'm getting:
If Rserve compiled in normal model (with forking) it throws error to stderr, but continues to work. However if it is running in "cooperative" mode R process dies after throwing this error. Not sure what is happening there.
I use Rserve http interface.
The text was updated successfully, but these errors were encountered: