From 0e66c30294b14133290e9e16edc14aaffb5ce93c Mon Sep 17 00:00:00 2001 From: wlandau Date: Wed, 13 Nov 2024 13:13:59 -0500 Subject: [PATCH] vignette --- inst/WORDLIST | 1 + vignettes/plugins.Rmd | 4 +++- 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/inst/WORDLIST b/inst/WORDLIST index edfff480..8ce22d00 100644 --- a/inst/WORDLIST +++ b/inst/WORDLIST @@ -24,6 +24,7 @@ Kirill's Kirill’s Kretch Kubernetes +retryable L'Ecuyer LFS LSF diff --git a/vignettes/plugins.Rmd b/vignettes/plugins.Rmd index ab51d721..c36ddef7 100644 --- a/vignettes/plugins.Rmd +++ b/vignettes/plugins.Rmd @@ -100,7 +100,9 @@ launcher$call( # Worker retries -The `launch_worker()` method can call `self$crashes(index = worker)` to get the number of consecutive times the worker has crashed (exited without completing all its tasks). You can use the crash count to assign more memory, CPU cores, or other resources to a worker launch. Here is a pseudo-code sketch which increases available memory by 4 GB each time a worker crashes, then resets back to the original 16 GB when the worker succeeds: +The `launch_worker()` method can call `self$crashes(index = worker)` to get the number of consecutive times the worker has crashed (exited without completing all its tasks). When a worker crashes, its crash count increments by 1. The next time a worker does not crash (exits only after completing all its tasks) the crash count resets back to zero. + +You can use the crash count to assign more memory, CPU cores, or other resources to a worker launch. Here is a pseudo-code sketch which increases available memory by 4 GB each time a worker crashes, then resets back to the original 16 GB when the worker succeeds: ```r launch_worker = function(call, name, launcher, worker, instance) {