You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Defines a multiplier that is used to calculate the number of threads used by the event subsystem. This property is only used when [`dt.worker.threads`](#dtworkerthreads) is set to 0. A machine with 4 cores and a multiplier of 4, will use (at most) 16 worker threads.
1699
+
Defines whether the task scheduler should be enabled. <br/><br/> May be disabled on specific nodes in the cluster to limit the amount of background processing they're doing. Can help with dedicating nodes to only serve web traffic.
Defines the number of worker threads that the event subsystem will consume. Events occur asynchronously and are processed by the Event subsystem. This value should be large enough to handle most production situations without introducing much delay, yet small enough not to pose additional load on an already resource-constrained server. A value of 0 will instruct Alpine to allocate 1 thread per CPU core. This can further be tweaked using the [`dt.worker.thread.multiplier`](#dtworkerthreadmultiplier) property.
1709
+
Defines the interval in milliseconds in which the task scheduler polls the database for due tasks.
Defines how long, in milliseconds, the task scheduler waits for running tasks to complete during shutdown. Tasks still running when this elapses are left in place and picked up by another node once their heartbeat expires.
Defines whether the task scheduler should be enabled. <br/><br/> May be disabled on specific nodes in the cluster to limit the amount of background processing they're doing. Can help with dedicating nodes to only serve web traffic.
1729
+
Defines the number of threads the task scheduler uses to execute due tasks. This is the maximum number of scheduled tasks that may run concurrently on a single node. <br/><br/> The scheduled task volume is low, but a few tasks can be long-running, so the value should be large enough to keep one slow task from blocking others. <br/><br/> Note that the grunt of asynchronous work is performed by the dex engine, not by the task scheduler. This is the wrong knob to tweak in most cases.
Maximum duration in ISO 8601 format for which the EPSS mirror task will hold a lock. <br/><br/> The duration should be long enough to cover the task's execution duration.
Minimum duration in ISO 8601 format for which the EPSS mirror task will hold a lock. <br/><br/> The duration should be long enough to cover eventual clock skew across API server instances.
Maximum duration in ISO 8601 format for which the internal component identification task will hold a lock. <br/><br/> The duration should be long enough to cover the task's execution duration.
Minimum duration in ISO 8601 format for which the internal component identification task will hold a lock. <br/><br/> The duration should be long enough to cover eventual clock skew across API server instances.
Maximum duration in ISO 8601 format for which the metrics maintenance task will hold a lock. <br/><br/> The duration should be long enough to cover the task's execution duration.
Minimum duration in ISO 8601 format for which the metrics maintenance task will hold a lock. <br/><br/> The duration should be long enough to cover eventual clock skew across API server instances.
Maximum duration in ISO 8601 format for which the portfolio vulnerability analysis task will hold a lock. <br/><br/> The duration should be long enough to cover the task's execution duration.
Minimum duration in ISO 8601 format for which the portfolio vulnerability analysis task will hold a lock. <br/><br/> The duration should be long enough to cover eventual clock skew across API server instances.
Cron expression of the workflow maintenance task. <br/><br/> The task: <ul> <li>Transitions workflow steps from <code>PENDING</code> to <code>TIMED_OUT</code> state</li> <li>Transitions workflow steps from <code>TIMED_OUT</code> to <code>FAILED</code> state</li> <li>Transitions children of <code>FAILED</code> steps to <code>CANCELLED</code> state</li> <li>Deletes finished workflows according to the configured retention duration</li> </ul>
Maximum duration in ISO 8601 format for which the workflow maintenance task will hold a lock. <br/><br/> The duration should be long enough to cover the task's execution duration.
Minimum duration in ISO 8601 format for which the workflow maintenance task will hold a lock. <br/><br/> The duration should be long enough to cover eventual clock skew across API server instances.
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4&size=40){kind=avatar}
0 commit comments