Hi Fabrice. It's an interesting concept that you have to use the F5 to direct traffic based on certain times of the day. Unfortunately, I believe what the F5 points at is just the gateway as the entry point on your primary and worker. And any internal balancing can only be handled via the internals of Tableau Server. Is it possible to run the backgrounders overnight with 0 vizql's, and then early morning adjust the # of vizql's on the worker to whatever is good for user interaction? I think you can adjust the # of vizql's with tabadmin set (I don't have the specifics right now handy) followed by a tabadmin config, tabadmin restart?
What would be the point of having an external load balancer if Tableau
doesn't stop its internal load balancing when configured ?
I have one gateway for each node and I expect Tableau to stop load
balancing provedid I declared the load balancing is made by my F5.
Stop and start of our production system is not an option.
Right. The external load balancer has limited influence on what it balances. See this link where it states that it distributes requests across gateways. From the gateway, Tableau load balancing takes over.
So why have an external load balancer in the first place? Using a combination of the F5 external load balancer and Tableau's H.A. architecture, it allows for resiliency in case one of the nodes should be unavailable.
Adding a load balancer: Add a Load Balancer
High availabiltiy: High Availability
Here are a couple of links that you might find useful: