This feature request is specifically for interactive sessions rather than batch jobs.
I can imagine many scenarios in which a user may want to extend the time limit of an interactive session - e.g. a long-running analysis job is taking longer than they expected, or perhaps they did not think at all about adjusting the time limit when they started the session.
In our clusters, interactive sessions (e.g. for Jupyter Notebooks) often run on “cheap” queues, where there isn’t really much competition for resources, and we could easily afford granting users an extension of a job without upsetting someone else.
Furthermore, in contrast to batch jobs, interactive jobs involve user input and it can be significantly harder / more time-consuming for users to recreate the state of the job after the previous one is killed due to a wall-time constraint.
In a cloud context in particular, interactive sessions are a resource- and cost-effective alternative to “always-on” workstations, and having an “Extend” button could help reduce anxiety of users in switching to such a model.
For select queues, add an “Extend” button to the interactive sessions list
I am aware that extending job durations on HPC schedulers typically requires admin privileges, but perhaps one could build a solution via
/etc/sudoers that allows users to run a restricted set of commands as administrator?
E.g. for the case of slurm, a locked-down
scontrol update on a hardcoded queue that allows them to add time to an existing job their user owns.
This may not be admissible in every security context, but could work in some. And perhaps there are better solutions.