You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When I try a fast function, like a regression with mtcars, PSOCK woks well on DigitalOcean droplets. But, if I connect to an S3 space, PSOCK returns this error
Failed to retrieve the value of ClusterFuture (<none>) from cluster RichSOCKnode #1 (PID 2009 on ‘143.110.238.244’). The reason reported was ‘error reading from connection’
When I try a fast function, like a regression with mtcars, PSOCK woks well on DigitalOcean droplets. But, if I connect to an S3 space, PSOCK returns this error ...
It sounds like you're implying that a "slow" function gives the error. I don't see how the processing time would result in error reading from connection. There is a timeout argument to parallelly::makeClusterPSOCK() that would trigger a timeout error for very long run times, but we're talking about 30 days or more.
Instead, I guess that one of your parallel workers crashes/core dumps for one reason or the other, e.g. running out of memory. If that happens, you'll get the same error message, e.g.
BTW, what does traceback() report after you get that error.
I recommend that you try to reproduce the problem with a smaller example using a smaller data set with fewer package dependencies. You could also add near-live progress updates using progressr to narrow how far the function calls get before you get that error.
Describe the bug
When I try a fast function, like a regression with mtcars, PSOCK woks well on DigitalOcean droplets. But, if I connect to an S3 space, PSOCK returns this error
Reproduce example
Expected behavior
It should have returned lm object. I tested the code by running it from ssh (terminal) on each droplet , and it works.
Session information
I tested both on laptop and server
Laptop: Pop!_OS 21.04
Server: Ubuntu Server 20.04
The text was updated successfully, but these errors were encountered: