2 of 2 people found this helpful
It will save the extract onto whatever nodes you have the dataengine process active. It replicates the created extract via the filestore process which also keeps the data in sync across the distributed dataengine processes. If a node only has the vizql process and no dataengine process, then Tableau will route traffic to one of the other nodes where the dataengine is active in order to retrieve the required info.
1. It will save onto the node where the backgrounder processed only if there is an active dataengine process
2. It will share internally within the cluster dependent on where the dataengine process(es) live. Tableau knows how to communicate across the cluster via the cluster controller
3. If you have the dataengine process allocated on other workers, then you should be ok as the filestore process has replicated the data and kept it in sync. See High Availability for more info
4. Either vizql can talk with data extracts on whatever node they live on, or the filestore replicates it to the specific nodes
5. Not sure what you mean
6. Yes, if the dataengine is allocated on other workers
Thank you for the response Jeff, This cleared some of my doubts.
Hi Jeff Strauss,
Thank you for the information that you have shared. Just a follow-up question regarding this. Please note that we currently have 4 worker nodes.
1. You have said that upon successful extract in Worker A, it will sync all the data to all remaining workers and it will be redundant across all workers. With that said, can we reduce the # of worker nodes without affecting the performance of the server? I am looking for ways to help our company save some money in infrastructure to be able to allot more money in buying server licenses.
2. Can you provide a recommendation for the settings/configuration of the Tableau Server with 4 worker nodes? (I know there is a documentation regarding this but I can't fully understand it. Sorry)
Hoping for a favorable response on this one. Thank you.