LSF/OpenLava template: Signal SIGINT by default to allow R to catch it gracefully
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- hpc, r
- Domain
- distributed-systems
Research direction
Start by locating the default LSF/OpenLava template and its handling of the wa and wt resources. Verify that the defaults request SIGINT 1 minute before the run-time limit while preserving user-provided values; done when the generated submission uses those defaults and existing overrides still work.
Written by the indexing model from the issue text.
Description
When a job is approaching it's maximum run-time limit, LSF sends a SIGINT 10 seconds before sending a SIGKILL (abrupt; not capturable).
R code can handle the SIGINT, but the 10-second heads up might be a bit tight. To adjust this, we can use LSF options -wa <action> and -wt <minutes>, e.g. -wa INT -wt 1 will give us a 60-second heads up.
Idea
Update the default LSF template to signal SIGINT 60 seconds in advance. Something like:
<%
## Signal SIGINT 60 seconds (1 minute) before the run-time limit
if (is.null(resources[["wa"]])) {
resources[["wa"]] <- "INT"
}
if (is.null(resources[["wt"]])) {
resources[["wt"]] <- 1
}
%>
- Dominant language
- R
- Stars
- 87
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from futureverse/future.batchtools
-
feature/resources scheduler/sge
Difficulty 4/5 3-5 days Newbie friendliness 50/100
futureverse/future.batchtools#104 · 1 comment ·
-
feature/resources scheduler/slurm
Difficulty 3/5 1-2 days Newbie friendliness 66/100
futureverse/future.batchtools#103 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
futureverse/future.batchtools#102 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 15/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
All issues in futureverse/future.batchtools
Similar issues
-
bug triage_needed
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pharmaverse/rtables#1123 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Trying to reassign a reactiveVal to the name of an existing reactiveVal doesn't overwrite the latter Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100