R: *[Experimental]* Create a controller with a LSF launcher.

crew_controller_lsf {crew.cluster}

R Documentation

Create a controller with a LSF launcher.

Description

Create an R6 object to submit tasks and launch workers on LSF workers.

Usage

crew_controller_lsf(
  name = NULL,
  workers = 1L,
  host = NULL,
  port = NULL,
  tls = crew::crew_tls(mode = "automatic"),
  tls_enable = NULL,
  tls_config = NULL,
  seconds_interval = 0.25,
  seconds_timeout = 60,
  seconds_launch = 86400,
  seconds_idle = Inf,
  seconds_wall = Inf,
  seconds_exit = NULL,
  retry_tasks = TRUE,
  tasks_max = Inf,
  tasks_timers = 0L,
  reset_globals = TRUE,
  reset_packages = FALSE,
  reset_options = FALSE,
  garbage_collection = FALSE,
  launch_max = 5L,
  verbose = FALSE,
  command_submit = as.character(Sys.which("bsub")),
  command_terminate = as.character(Sys.which("bkill")),
  command_delete = NULL,
  script_directory = tempdir(),
  script_lines = character(0L),
  lsf_cwd = getwd(),
  lsf_log_output = "/dev/null",
  lsf_log_error = "/dev/null",
  lsf_memory_gigabytes_limit = NULL,
  lsf_memory_gigabytes_required = NULL,
  lsf_cores = NULL
)

Arguments

`name`	Name of the client object. If `NULL`, a name is automatically generated.
`workers`	Integer, maximum number of parallel workers to run.
`host`	IP address of the `mirai` client to send and receive tasks. If `NULL`, the host defaults to the local IP address.
`port`	TCP port to listen for the workers. If `NULL`, then an available ephemeral port is automatically chosen.
`tls`	A TLS configuration object from `crew_tls()`.
`tls_enable`	Deprecated on 2023-09-15 in version 0.4.1. Use argument `tls` instead.
`tls_config`	Deprecated on 2023-09-15 in version 0.4.1. Use argument `tls` instead.
`seconds_interval`	Number of seconds between polling intervals waiting for certain internal synchronous operations to complete, such as checking `mirai::status()`
`seconds_timeout`	Number of seconds until timing out while waiting for certain synchronous operations to complete, such as checking `mirai::status()`.
`seconds_launch`	Seconds of startup time to allow. A worker is unconditionally assumed to be alive from the moment of its launch until `seconds_launch` seconds later. After `seconds_launch` seconds, the worker is only considered alive if it is actively connected to its assign websocket.
`seconds_idle`	Maximum number of seconds that a worker can idle since the completion of the last task. If exceeded, the worker exits. But the timer does not launch until `tasks_timers` tasks have completed. See the `idletime` argument of `mirai::daemon()`. `crew` does not excel with perfectly transient workers because it does not micromanage the assignment of tasks to workers, so please allow enough idle time for a new worker to be delegated a new task.
`seconds_wall`	Soft wall time in seconds. The timer does not launch until `tasks_timers` tasks have completed. See the `walltime` argument of `mirai::daemon()`.
`seconds_exit`	Deprecated on 2023-09-21 in version 0.1.2.9000. No longer necessary.
`retry_tasks`	`TRUE` to automatically retry a task in the event of an unexpected worker exit. `FALSE` to give up on the first exit and return a `mirai` error code (code number 19). `TRUE` (default) is recommended in most situations. Use `FALSE` for debugging purposes, e.g. to confirm that a task is causing a worker to run out of memory or crash in some other way.
`tasks_max`	Maximum number of tasks that a worker will do before exiting. See the `maxtasks` argument of `mirai::daemon()`. `crew` does not excel with perfectly transient workers because it does not micromanage the assignment of tasks to workers, it is recommended to set `tasks_max` to a value greater than 1.
`tasks_timers`	Number of tasks to do before activating the timers for `seconds_idle` and `seconds_wall`. See the `timerstart` argument of `mirai::daemon()`.
`reset_globals`	`TRUE` to reset global environment variables between tasks, `FALSE` to leave them alone.
`reset_packages`	`TRUE` to unload any packages loaded during a task (runs between each task), `FALSE` to leave packages alone.
`reset_options`	`TRUE` to reset global options to their original state between each task, `FALSE` otherwise. It is recommended to only set `reset_options = TRUE` if `reset_packages` is also `TRUE` because packages sometimes rely on options they set at loading time.
`garbage_collection`	`TRUE` to run garbage collection between tasks, `FALSE` to skip.
`launch_max`	Positive integer of length 1, maximum allowed consecutive launch attempts which do not complete any tasks. Enforced on a worker-by-worker basis. The futile launch count resets to back 0 for each worker that completes a task. It is recommended to set `launch_max` above 0 because sometimes workers are unproductive under perfectly ordinary circumstances. But `launch_max` should still be small enough to detect errors in the underlying platform.
`verbose`	Logical, whether to see console output and error messages when submitting worker.
`command_submit`	Character of length 1, file path to the executable to submit a worker job.
`command_terminate`	Character of length 1, file path to the executable to terminate a worker job. Set to `""` to skip manually terminating the worker. Unless there is an issue with the platform, the job should still exit thanks to the NNG-powered network programming capabilities of `mirai`. Still, if you set `command_terminate = ""`, you are assuming extra responsibility for manually monitoring your jobs on the cluster and manually terminating jobs as appropriate.
`command_delete`	Deprecated on 2024-01-08 (version 0.1.4.9001). Use `command_terminate` instead.
`script_directory`	Character of length 1, directory path to the job scripts. Just before each job submission, a job script is created in this folder. Script base names are unique to each launcher and worker, and the launcher deletes the script when the worker is manually terminated. `tempdir()` is the default, but it might not work for some systems. `tools::R_user_dir("crew.cluster", which = "cache")` is another reasonable choice.
`script_lines`	Optional character vector of additional lines to be added to the job script just after the more common flags. An example would be `script_lines = "module load R"` if your cluster supports R through an environment module.
`lsf_cwd`	Character of length 1, directory to launch the worker from (as opposed to the system default). `lsf_cwd = "/home"` translates to a line of `⁠#BSUB -cwd /home⁠` in the LSF job script. `lsf_cwd = getwd()` is the default, which launches workers from the current working directory. Set `lsf_cwd = NULL` to omit this line from the job script.
`lsf_log_output`	Character of length 1, file pattern to control the locations of the LSF worker log files. By default, both standard output and standard error go to the same file. `lsf_log_output = "crew_log_%J.log"` translates to a line of `⁠#BSUB -o crew_log_%J.log⁠` in the LSF job script, where `⁠%J⁠` is replaced by the job ID of the worker. The default is `⁠/dev/null⁠` to omit these logs. Set `lsf_log_output = NULL` to omit this line from the job script.
`lsf_log_error`	Character of length 1, file pattern for standard error. `lsf_log_error = "crew_error_%J.err"` translates to a line of `⁠#BSUB -e crew_error_%J.err⁠` in the LSF job script, where `⁠%J⁠` is replaced by the job ID of the worker. The default is `⁠/dev/null⁠` to omit these logs. Set `lsf_log_error = NULL` to omit this line from the job script.
`lsf_memory_gigabytes_limit`	Positive numeric of length 1 with the limit in gigabytes `lsf_memory_gigabytes_limit = 4` translates to a line of `⁠#BSUB -M 4G⁠` in the LSF job script. `lsf_memory_gigabytes_limit = NULL` omits this line.
`lsf_memory_gigabytes_required`	Positive numeric of length 1 with the memory requirement in gigabytes `lsf_memory_gigabytes_required = 4` translates to a line of `⁠#BSUB -R 'rusage[mem=4G]'⁠` in the LSF job script. `lsf_memory_gigabytes_required = NULL` omits this line.
`lsf_cores`	Optional positive integer of length 1, number of CPU cores for the worker. `lsf_cores = 4` translates to a line of `⁠#BSUB -n 4⁠` in the LSF job script. `lsf_cores = NULL` omits this line.

Details

WARNING: the crew.cluster LSF plugin is experimental and has not actually been tested on a LSF cluster. Please proceed with caution and report bugs to https://github.com/wlandau/crew.cluster.

Attribution

The template files at https://github.com/mschubert/clustermq/tree/master/inst informed the development of the crew launcher plugins in crew.cluster, and we would like to thank Michael Schubert for developing clustermq and releasing it under the permissive Apache License 2.0. See the NOTICE and README.md files in the crew.cluster source code for additional attribution.

Examples

if (identical(Sys.getenv("CREW_EXAMPLES"), "true")) {
controller <- crew_controller_lsf()
controller$start()
controller$push(name = "task", command = sqrt(4))
controller$wait()
controller$pop()$result
controller$terminate()
}

[Package crew.cluster version 0.3.2 Index]