ClearML/clearml-docs
1
0
Fork 0
mirror of https://github.com/clearml/clearml-docs synced 2025-04-15 05:04:31 +00:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Clarify Non-responsive Task Watchdog section (#1072)
Some checks are pending
CI / build (push) Waiting to run
Details

Browse Source
This commit is contained in:
pollfly 2025-03-05 16:39:16 +02:00 committed by GitHub
parent f130d3d758
commit 1a979a521e
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 17 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
docs/deploying_clearml/clearml_server_config.md
View File

@ -361,10 +361,16 @@ You can also use hashed passwords instead of plain-text passwords. To do that:
### Non-responsive Task Watchdog
The non-responsive task watchdog monitors tasks that were not updated for a specified time interval, and then
the watchdog marks them as `aborted`. The non-responsive experiment watchdog is always active.
The non-responsive task watchdog monitors for running tasks that have stopped communicating with the ClearML Server for a specified
time interval. If a task remains unresponsive beyond the set threshold, the watchdog marks it as `aborted`.
Modify the following settings for the watchdog:
A task is considered non-responsive if the time since its last communication with the ClearML Server exceeds the
configured threshold. The watchdog starts counting after each successful communication with the server. If no further
updates are received within the specified time, the task is considered non-responsive. This typically happens if:
* The task's main process is stuck but has not exited.
* There is a network issue preventing the task from communicating with the server.
You can configure the following watchdog settings:
* Watchdog status - enabled / disabled
* The time threshold (in seconds) of experiment inactivity (default value is 7200 seconds (2 hours)).
@ -372,10 +378,15 @@ Modify the following settings for the watchdog:
**To configure the non-responsive watchdog for the ClearML Server:**
1. In the ClearML Server `/opt/clearml/config/services.conf` file, add or edit the `tasks.non_responsive_tasks_watchdog`
section and specify the watchdog settings.
1. Open the ClearML Server `/opt/clearml/config/services.conf` file.
:::tip
If the `services.conf` file does not exist, create your own in ClearML Server's `/opt/clearml/config` directory (or
an alternate folder you configured).
:::
1. Add or edit the `tasks.non_responsive_tasks_watchdog` section and specify the watchdog settings. For example:
For example:
```
tasks {
non_responsive_tasks_watchdog {
@ -389,11 +400,6 @@ Modify the following settings for the watchdog:
}
}
```
:::tip
If the `services.conf` file does not exist, create your own in ClearML Server's `/opt/clearml/config` directory (or
an alternate folder you configured), and input the modified configuration
:::
1. Restart ClearML Server.