-
Notifications
You must be signed in to change notification settings - Fork 10
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
Future ('<none>') expired #31
Comments
I don't know LSF, but the message (which is not from anywhere in the future ecosystem):
looks similar to messages received when schedulers such as Torque & SGE decides to terminate a job. Could it be that you hitting the LSF scheduler with too many jobs in a short period of time? Do you have a sysadm that might help you look into the local logs? By the default, > plan(batchtools_lsf)
> nbrOfWorkers()
[1] Inf This means that there's no limit in the number of jobs the future framework can submit - it'll just keep submitting jobs to scheduler as more futures are created. You can limit this by specifying: > plan(batchtools_lsf, workers = 50)
> nbrOfWorkers()
[1] 50 That way there will be at most 50 jobs on the queue (running or queued). That might help you avoid the problem. |
Hey Henrik, I already had the suspicion it's rather a problem with the HPC itself than with Thanks a lot. |
Hey Henrik,
I'm using
future.batchtools
to submit jobs to a HPC with LSF. When only submitting a rather small amount of jobs everything is running smoothly, however, if I increase the number of submitted jobs I get the following error:When looking into the .future - folder many jobs seem to be alright, but still at least one job is failing with the following log
I use
future.batchtools_0.7.1-9000
,future_1.9.0
andfurrr_0.1.0
.The text was updated successfully, but these errors were encountered: