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
At the moment, runners poll for playbook actions @every 1m. Once it runs it, the result is then pushed @every 15s.
Due to this, it takes at few minutes to complete a simple playbook with one action.
With more actions, time to complete increases linearly.
Proposed solutions
Long polling
Runners shouldn't run on a schedule. Rather they should be continuously polling for actions in a never ending for loop.
Stateful connection
Somehow maintain a stateful TCP connection between the upstream and the runner.
Runners "subscribe" to upstream on startup and upstream "publishes" to the connection whenever a new action for that agent is inserted to db.
The text was updated successfully, but these errors were encountered:
At the moment, runners poll for playbook actions
@every 1m
. Once it runs it, the result is then pushed@every 15s
.Due to this, it takes at few minutes to complete a simple playbook with one action.
With more actions, time to complete increases linearly.
Proposed solutions
Runners shouldn't run on a schedule. Rather they should be continuously polling for actions in a never ending for loop.
Somehow maintain a stateful TCP connection between the upstream and the runner.
Runners "subscribe" to upstream on startup and upstream "publishes" to the connection whenever a new action for that agent is inserted to db.
The text was updated successfully, but these errors were encountered: