Skip to content

Commit 88173db

Browse files
committed
Update configuration section
1 parent f93092a commit 88173db

1 file changed

Lines changed: 7 additions & 0 deletions

File tree

configuration.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,7 @@ The configuration file is the only argument passed to ElastiSim and defines the
1616
| ``schedule_on_job_submit`` | Whether a job submission triggers a scheduling algorithm invocation | bool | false | Yes, if ``scheduling_interval`` is false |
1717
| ``schedule_on_job_finalize`` | Whether a job finalization triggers a scheduling algorithm invocation | bool | false | Yes, if ``scheduling_interval`` is false |
1818
| ``schedule_on_scheduling_point`` | Whether a job reaching a scheduling point triggers a scheduling algorithm invocation | bool | false | No |
19+
| ``schedule_on_reconfiguration`` | Whether a job reconfiguration triggers a scheduling algorithm invocation | bool | false | No |
1920
| ``scheduling_interval`` | Invocation interval of the scheduling algorithm | integer (seconds) | 0 (disabled) | Yes, if ``schedule_on_job_submit`` or ``schedule_on_job_finalize`` is false |
2021
| ``min_scheduling_interval`` | Minimum time between two scheduling algorithm invocations | integer (seconds) | 0 (disabled) | No |
2122
| ``allow_oversubscription`` | Whether the scheduler can oversubscribe compute nodes with multiple jobs | bool | false | No |
@@ -39,6 +40,12 @@ The configuration file is the only argument passed to ElastiSim and defines the
3940
{: .warning }
4041
Setting the sensing interval too small can significantly increase simulation times, as the discrete-event simulation engine will fire an event at each sensing interval. Logging task times can also introduce a significant overhead.
4142

43+
{: .note }
44+
ElastiSim supports node migration (i.e., transferring nodes from one job to another) in a single scheduling step when the decision is taken at an invocation triggered by a scheduling point (requires ``schedule_on_scheduling_point`` to be ``true``) or evolving request.
45+
46+
{: .important }
47+
``schedule_on_reconfiguration`` triggers the scheduling algorithm _after_ applying a **pending** resource reconfiguration but _before_ executing a potential ``on_reconfiguration`` or ``on_expansion`` phase. This invocation trigger enables scheduling decisions when resources change their state, such as nodes becoming free after a shrink operation when a job reaches its next scheduling point. However, a job reconfigured during a scheduling point or evolving request will not trigger the algorithm again when the reconfiguration is applied.
48+
4249
## Example configuration
4350

4451
```json

0 commit comments

Comments
 (0)