io.quarkiverse.temporal.config.WorkerRuntimeConfig.jdp Maven / Gradle / Ivy
io.quarkiverse.temporal.config.WorkerRuntimeConfig.defaultDeadlockDetectionTimeout=Time period in ms that will be used to detect workflows deadlock. Default is 1000ms, which is chosen if set to zero.\nSpecifies an amount of time in milliseconds that workflow tasks are allowed to execute without interruption. If workflow\ntask runs longer than specified interval without yielding (like calling an Activity), it will fail automatically.
io.quarkiverse.temporal.config.WorkerRuntimeConfig.defaultHeartbeatThrottleInterval=The default amount of time between sending each pending heartbeat to the server. This is used if the ActivityOptions do\nnot provide a HeartbeatTimeout. Otherwise, the interval becomes a value a bit smaller than the given HeartbeatTimeout.\nDefault is 30s, which is chosen if set to null or 0.
io.quarkiverse.temporal.config.WorkerRuntimeConfig.disableEagerExecution=Disable eager activities. If set to true, eager execution will not be requested for activities requested from workflows\nbound to this Worker.\nEager activity execution means the server returns requested eager activities directly from the workflow task back to this\nworker which is faster than non-eager which may be dispatched to a separate worker.\nDefaults to false, meaning that eager activity execution is permitted
io.quarkiverse.temporal.config.WorkerRuntimeConfig.identity=Override identity of the worker primary specified in a WorkflowClient options.
io.quarkiverse.temporal.config.WorkerRuntimeConfig.localActivityWorkerOnly=If set to true worker would only handle workflow tasks and local activities. Non-local activities will not be executed by\nthis worker.\nDefault is false.
io.quarkiverse.temporal.config.WorkerRuntimeConfig.maxConcurrentActivityExecutionSize=Maximum number of activities executed in parallel. Default is 200, which is chosen if set to zero.
io.quarkiverse.temporal.config.WorkerRuntimeConfig.maxConcurrentActivityTaskPollers=Number of simultaneous poll requests on activity task queue. Consider incrementing if the worker is not throttled due to\n`MaxActivitiesPerSecond` or `MaxConcurrentActivityExecutionSize` options and still cannot keep up with the request rate.\nDefault is 5, which is chosen if set to zero.
io.quarkiverse.temporal.config.WorkerRuntimeConfig.maxConcurrentLocalActivityExecutionSize=Maximum number of local activities executed in parallel. Default is 200, which is chosen if set to zero.
io.quarkiverse.temporal.config.WorkerRuntimeConfig.maxConcurrentWorkflowTaskExecutionSize=Maximum number of simultaneously executed workflow tasks. Default is 200, which is chosen if set to zero.
io.quarkiverse.temporal.config.WorkerRuntimeConfig.maxConcurrentWorkflowTaskPollers=Sets the maximum number of simultaneous long poll requests to the Temporal Server to retrieve workflow tasks. Changing\nthis value will affect the rate at which the worker is able to consume tasks from a task queue.\nDue to internal logic where pollers alternate between sticky and non-sticky queues, this value cannot be 1 and will be\nadjusted to 2 if set to that value.\nDefault is 5, which is chosen if set to zero.
io.quarkiverse.temporal.config.WorkerRuntimeConfig.maxHeartbeatThrottleInterval=The maximum amount of time between sending each pending heartbeat to the server. Regardless of heartbeat timeout, no\npending heartbeat will wait longer than this amount of time to send. Default is 60s, which is chosen if set to null or 0.
io.quarkiverse.temporal.config.WorkerRuntimeConfig.maxTaskQueueActivitiesPerSecond=Sets the rate limiting on number of activities that can be executed per second. This is managed by the server and\ncontrols activities per second for the entire task queue across all the workers. Notice that the number is represented in\ndouble, so that you can set it to less than 1 if needed. For example, set the number to 0.1 means you want your activity\nto be executed once every 10 seconds. This can be used to protect down stream services from flooding. The zero value of\nthese uses the default value. Default is unlimited.
io.quarkiverse.temporal.config.WorkerRuntimeConfig.maxWorkerActivitiesPerSecond=Maximum number of activities started per second by this worker. Default is 0 which means unlimited.
io.quarkiverse.temporal.config.WorkerRuntimeConfig.stickyQueueScheduleToStartTimeout=Timeout for a workflow task routed to the "sticky worker" - host that has the workflow instance cached in memory. Once it\ntimes out, then it can be picked up by any worker.\nDefault value is 5 seconds.
io.quarkiverse.temporal.config.WorkerRuntimeConfig.stickyTaskQueueDrainTimeout=During graceful shutdown, as when calling WorkerFactory. shutdown(), if the workflow cache is enabled, this timeout\ncontrols how long to wait for the sticky task queue to drain before shutting down the worker. If set the worker will stop\nmaking new poll requests on the normal task queue, but will continue to poll the sticky task queue until the timeout is\nreached. This value should always be greater than clients rpc long poll timeout, which can be set via\nWorkflowServiceStubsOptions. Builder. setRpcLongPollTimeout(Duration).\nDefault is not to wait.
io.quarkiverse.temporal.config.WorkerRuntimeConfig.taskQueue=Task queue name worker uses to poll. It uses this name for both workflow and activity task queue polls. Default is worker\nname
io.quarkiverse.temporal.config.WorkerRuntimeConfig.useBuildIdForVersioning=Opts the worker in to the Build-ID-based versioning feature. This ensures that the worker will only receive tasks which\nit is compatible with. For more information see\: TODO\: Doc link\nDefaults to false