-
1. Re: TabElastic
A nice concept Mike. its like a scaling group which can scale process on-demand based on loads.
Would you be providing the tool as downloads soon!?
Regards
Shankar
-
2. Re: TabElastic
I like the concept but if I understand what's being published on GitHub, you need to restart Tableau Server in the process.
How do the users feel about this?
(Tableau, please let us create and end process without restarting the whole service).
-
3. Re: TabElastic
1 of 1 people found this helpfulThe code is on Github (linked in the write-up): https://github.com/ps-data/ps-analytics-public/blob/master/tabElastic
let me know if there are any questions.
Best,
Mike
-
4. Re: TabElastic
Agree, Damien
We are restarting and it takes about 5 minutes for services to come back up. When we do it, it's early and users barely notice. It's also a great time to do a tabadmin cleanup.
Right now, it's on our dev box which does a lot of the processing for workbooks, data sources and the like so, again, users rarely notice.
Hope that helps.
-Mike
-
5. Re: TabElastic
Hi Mike
How does it work for cluster environment? Does it have option to balance the process across clusters. That is something which will make it even powerful.
Keep up the awesome work!
Shanky
-
6. Re: TabElastic
1 of 1 people found this helpfulShanky,
You read my mind. That's the next step. Of course, we want to take the situations of the environment and base the config accordingly (eg: view heavy vs extract heavy).
Keep an eye out and I'll post back once we're completed.
The cluster env is also on the horizon for the automated server install: https://github.com/ps-data/ps-analytics-public/blob/master/TsServerUpgrade
Let me know what questions you have.
-Mike Roberts
-
7. Re: TabElastic
2 of 2 people found this helpfulThis is a great idea, and although having to restart the machine after the reset is a bummer, you can dramatically simplify that script and avoid the potential of Tableau changing that UI.
Instead of relying on individual windows and keystrokes, you can simply use tabadmin set to adjust those workers.
tabadmin stop
tabadmin set worker0.backgrounder.procs #
tabadmin configure
tabadmin start