Skip to content

Document how to apply updated scheduler templates #335

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.

Sign up for GitHub

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

Merged
jemus42 merged 2 commits into from
Oct 7, 2026
Merged

Document how to apply updated scheduler templates #335

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0513338
document how to reload updated templates
n3orma Oct 2, 2026
3c44faf
docs: document reloading registry configuration
n3orma Oct 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions R/loadRegistry.R
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,15 @@
#' loaded into the global environment when the registry is loaded. Existing
#' objects with the same names may be overwritten.
#'
#' The configuration file specified by \code{conf.file} is sourced each time
#' the registry is loaded. This also reloads the cluster functions configured
#' there, so changes to the configuration or to a referenced scheduler template
#' can be applied by calling \code{loadRegistry()} again instead of recreating
#' the registry.
#'
#' Only jobs submitted with \code{\link{submitJobs}} after reloading the registry
#' use the updated configuration. Jobs that have already been submitted or
#' queued are not affected.
#' Multiple R sessions accessing the same registry simultaneously can lead to database inconsistencies.
#' This is especially dangerous if the same \code{file.dir} is accessed from multiple machines, e.g. via a mount.
#'
Expand Down
Loading