KNOWLEDGE BASE

Linked Tasked did not run immediately even if clicking "Run Now" button and the Backgrounder nodes which can run flows are all idle.


Published: 20 Aug 2023
Last Modified Date: 28 Aug 2023

Issue

When setting some Backgrounder node roles to make some of them only run flows and the other ones only run the non-flow jobs,
If the Backgrounder nodes which can run the non-flow jobs are all busy, the Linked Tasked flows can not be run immediately even if we click "Run Now" button and the Backgrounder nodes which can run flows are all idle.

For Example:
If there are 3 Backgrounder nodes node1, node2, node3 in the Tableau Server cluster,  node2 and node3 are set with "flows" node role to only run flow jobs, and node1 is set with "no-flows" node role to only run non-flow jobs, when the Backgrounder on node1 is busy with running some non-flow jobs such as some extract-refreshing jobs which take a long time to run, Even if you try to run Linked Tasked flow job by clicking "Run Now" button and the Backgrounders node2 and node3 are idle at  that time, the Linked Tasked flow job can not be run until the Backgrounder on node1 is idle.

Environment

  • Tableau Server with multi-nodes
  • Linked Task

Resolution

Option 1

Re-run your Linked Tasked flow job when the Backgrounder node which can run all jobs are idle.

Option 2

Change your Backgrounder nodes roles which only run flows from "flows" to "all-jobs".
For Example:
tsm topology set-node-role -n nodeX -r all-jobs

 

Cause

This is by design.
Linked Task contains the flow jobs and a system job named as "Linked Task Kickoff". The "Linked Task Kickoff" job need to be run at first before the flow jobs start running.
If your backgrounder nodes which can run system jobs are all busy with some other system jobs such as "Synching Active Directory" jobs, the "Linked Task Kickoff" job wiil be in the queue for a long time and will not be run on time.
Did this article resolve the issue?