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
{{ message }}
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.
The Scheduled Tasks included with the State Conductor (schedules.sjs, and waitTask.sjs) don't utilize a host setting. This causes these tasks to be executed on all hosts of a cluster at the scheduled times. This is problematic for scheduled State Conductor scoped state machines and wait tasks. These tasks should only operate on a single host in the cluster.
The waitTask has been refactored in #179 to operate only on the local forests of a host, and thus optimized for, and intended to run on all hosts of a cluster.
As such, this task issue should only apply to the scheduler task.
aclavio
changed the title
Scheduled Tasks (scheduler and waitTask) should only operate on a single host
Scheduled Tasks (scheduler) should only operate on a single host
Aug 16, 2021
The Scheduled Tasks included with the State Conductor (schedules.sjs, and
waitTask.sjs) don't utilize a host setting. This causes these tasks to be executed on all hosts of a cluster at the scheduled times. This is problematic for scheduled State Conductor scoped state machines and wait tasks. These tasks should only operate on a single host in the cluster.see: https://github.com/marklogic-community/ml-app-deployer/wiki/Scheduled-Tasks
The text was updated successfully, but these errors were encountered: