library(rush)
branin = function(x1, x2) {
(x2 - 5.1 / (4 * pi^2) * x1^2 + 5 / pi * x1 - 6)^2 + 10 * (1 - 1 / (8 * pi)) * cos(x1) + 10
}
wl_random_search = function(rush, branin) {
while (rush$n_finished_tasks < 100) {
xs = list(x1 = runif(1, -5, 10), x2 = runif(1, 0, 15))
key = rush$push_running_tasks(xss = list(xs))
tryCatch({
if (runif(1) < 0.5) stop("Random Error")
ys = list(y = branin(xs$x1, xs$x2))
rush$finish_tasks(key, yss = list(ys))
}, error = function(e) {
condition = list(message = e$message)
rush$fail_tasks(key, conditions = list(condition))
})
}
}rush provides error-handling mechanisms for two failure modes: standard R errors during task evaluation and unexpected worker failures such as crashes or lost connections. If errors cannot be caught automatically, the worker loop can be debugged locally.
Simple R Errors
We use the random search example from the tutorial and introduce a random error with 50% probability. Within the worker loop, users are responsible for catching errors and marking the corresponding task as "failed" using the $fail_tasks() method.
We initialize the network and start the workers.
rush = rsh(
network = "test-simple-error",
config = redux::redis_config())
mirai::daemons(4)
rush$start_workers(
worker_loop = wl_random_search,
n_workers = 4,
branin = branin)When an error occurs, the task is marked as "failed" and the error message is stored in the "message" column. This ensures that errors do not interrupt the overall execution and allows subsequent inspection and reevaluation of failed tasks.
rush$fetch_failed_tasks() x1 x2 worker_id condition keys
<num> <num> <char> <list> <char>
1: -2.9825885 1.998325 hygienic_b... <list[1]> 1a0c2b26-9...
2: -4.5441419 10.327300 hairraisin... <list[1]> 1ec813d8-1...
3: 4.7727800 11.802333 hairraisin... <list[1]> 3b2583a0-e...
4: 4.7373468 3.221746 stuck_cock... <list[1]> df1009a2-7...
5: 0.3925119 7.440330 stuck_cock... <list[1]> bf686a05-7...
---
75: -2.7437545 2.695191 hygienic_b... <list[1]> ab7b005c-9...
76: -0.7734533 13.197200 earthy_blu... <list[1]> 406eefc9-4...
77: -0.1002986 14.928041 hygienic_b... <list[1]> b8409868-0...
78: -4.5690976 3.465293 earthy_blu... <list[1]> 88dc8939-f...
79: 0.8858232 4.016169 hygienic_b... <list[1]> 6b61828f-7...Handling Failing Workers
When a worker fails due to a crash or lost connection, its tasks may remain in the "running" state indefinitely. We simulate a segmentation fault by terminating the worker process.
wl_failed_worker = function(rush) {
xs = list(x1 = runif(1, -5, 10), x2 = runif(1, 0, 15))
key = rush$push_running_tasks(xss = list(xs))
tools::pskill(Sys.getpid(), tools::SIGKILL)
}
rush = rsh(
network = "test-failed-workers",
config = redux::redis_config())
mirai::daemons(2)
worker_ids = rush$start_workers(
worker_loop = wl_failed_worker,
n_workers = 2)The $detect_lost_workers() method identifies such workers and updates their state to "terminated". For workers started with $start_local_workers() or $start_workers(), lost worker detection works automatically by checking process status. Workers started via $worker_script() require an additional heartbeat mechanism (see the manager vignette).
rush$detect_lost_workers()[1] "commonlaw_zopilote_f6037255" "lygophobic_thrasher_9812fd5c"When a worker fails, the state of any task it was evaluating is set to "failed".
rush$fetch_failed_tasks() x1 x2 worker_id condition keys
<num> <num> <char> <list> <char>
1: 2.883801 3.075386 commonlaw_... <list[1]> 9edf021e-d...
2: 2.588461 11.570943 lygophobic... <list[1]> 904923da-5...Debugging
When the worker loop fails due to an uncaught error, the loop can be executed locally to reproduce and inspect the failure. Consider the following worker loop, which generates an error for large values of x1.
To debug the worker loop locally, a RushWorker instance is instantiated manually and passed as argument to the worker loop.
rush_worker = RushWorker$new(network_id = "test-error")
wl_error(rush_worker)Error in `wl_error()`:
! Unexpected errorWhen an error is raised in the main process, traceback() can be called to examine the stack trace and breakpoints can be set within the worker loop to inspect the program state. Note that certain errors such as missing packages may not be reproducible locally but can be identified by running the worker loop in a separate process and using $detect_lost_workers().
rush = rsh(
network = "test-error",
config = redux::redis_config())
mirai::daemons(1)
rush$start_workers(
worker_loop = wl_error,
n_workers = 1)
rush$detect_lost_workers()[1] "transcendental_africanjacana_791bc46d"Output and message logs can be written to files via the message_log and output_log arguments.
rush = rsh(
network = "test-error",
config = redux::redis_config())
message_log = tempdir()
output_log = tempdir()
mirai::daemons(1)
worker_ids = rush$start_workers(
worker_loop = wl_error,
n_workers = 1,
message_log = message_log,
output_log = output_log)
Sys.sleep(5)
readLines(file.path(message_log, sprintf("message_%s.log", worker_ids[1])))[1] "Debug message logging on worker piteous_crustacean_9bbdbb0c started"[1] "[1] \"Debug output logging on worker piteous_crustacean_9bbdbb0c started\""