Skip to main content
GroupsInternational Server Admin (ISATUG)
Featured group

International Server Admin (ISATUG)

Tableau User Group | International Server Admin
Ask a question...
Nitin Kapoor
Jan 17, 2022, 11:54 AM
Need help for Root Cause Analysis for Slow Load times on Tableau Server

Hello Everyone!

Lately, there has been a considerable slowness in View Load Times on the Tableau server. This issue is limited to server only and not Desktop.

 

I have been trying to figure out what could be the root cause, however, no tool is helping me single out the same. It could be a heavy query choking the server, could be server side rendering, or some mistake in configuring the processes. (I have a 5 node cluster with dedicated VizQLs and Backgrounder nodes)

 

Please help me if I can use any tool to figure this out. (Resource Monitoring tool is part of Server management license, and hence i cannot use it).

 

Regards,

Nitin

2 answers
  1. Yuri Fal
    Jan 17, 2022, 12:37 PM

    Hi Nittin,

     

    I would recommend to make a snapshot of logs

    and feed them into the LogShark, then (after digesting)

    start the analyses with the Resource Manager workbook.

     

    https://github.com/tableau/logshark

     

    Yours,

    Yuri

Write an answer...
0/9000
Cody Stevens
Aug 15, 2024, 2:16 PM

Is anyone else experiencing high CPU usage by vizqlServer processes after upgrading to version 2024.2.1?

I upgraded our server to from 2023.3 to 2024.2.1 last Saturday and have already had to restart the environment twice due to vizqlServer processes holding CPU to the point where it has the server CPU at 100% usage for a very long time. In a 24 hour period the CPU did not drop below 50%. Before the upgrade average CPU usage over a 24 hour period was only 8%.

69 comments
  1. Shivam Kumar
    Aug 15, 2024, 3:32 PM

    VizQLs do consume lots of RAM, and the behavior is completely normal. there is no appreciable difference between the way they work in 2023.3 and 2024.2.1 so I'm not sure why you're seeing something different.

    When you watch the memory consumption on one (or more) machines over time, you'll typically see more and more RAM being used, and then it levels off. 

    You may ALSO see available RAM go "way back up" if Tableau Server chooses to recycle a vizqlserver process. The Server Resource Manager will do that from time to time. This behavior could explain why earlier on in the thread Toby saw one of his VizQLs using lots of RAM, and another "not so much". The process using less RAM was probably "newer" than the other, having recently been recycled.

Write a comment...
0/9000
Tableau Community Forums Member (Inactive) (Member of the Tableau Community Forums at Salesforce)
May 29, 2018, 2:31 PM
Server disk low fall under 20%

Hi All,

 

We are on Tableau server 10.4 .  3 node distribution   environments on windows server 2012 R2. Prepared  active repository on Worker1 running low disk space warning messages are getting as per specified in configuration  whenever  is below 20% space. I moved prepared repository on worker2 but still getting warning message due to space less then 20% on worker1.

log files C:\ProgramData\Tableau\Tableau Server\data\tabsvc\vizqlserver\Logs............................... not saving

and C:\ProgramData\Tableau\Tableau Server\data\tabsvc\temp...............................................................empty..........

since this on production box so every day backup scheduled on different drive.

Tableau 10.2 we never had any issue after upgrade 10.4 having this issue running out space on worker1 day by day.

configuration as attached Please advice.

 

Thank you.

RK

server image.docx
1 answer
  1. Matz Rasmus (Knowit Solutions Oy)
    Dec 11, 2024, 1:21 PM

    Hi,

     

    All data in the repository is still stored on worker1 as well even though it is not the preferred node. So the only way to fix this is to either remove the repository altogether from worker1, or increase the disk space.

Write an answer...
0/9000
John Krieg
Dec 2, 2024, 5:52 PM

Good morning Everyone,

We are now using a load balancer and no longer use the A Node (original node) for accessing the Workbooks/ Views/Data sources. Unfortunately, the Server continues to use the Original Node server address for ANY and ALL communications (specifically when an extract fails). Does anyone else have this issue and if so, how did you get the load balancer link in the email from the Tableau Server?

1 comment
  1. Emeric LE SAULNIER DE SAINT JOUAN (M2)
    Dec 3, 2024, 8:45 AM

    Hi @John Krieg​, it is a Tableau Server config thing. When I change the gateway dns, here are the update steps I take:

    tsm configuration set -k svcmonitor.notification.smtp.canonical_url -v "https://tableau.mynewdomain.com"
    tsm configuration set -k gateway.public.base_url  -v "https://tableau.mynewdomain.com"
    tsm configuration set -k gateway.public.host -v "tableau.mynewdomain.com"
    tsm configuration set -k gateway.public.port  -v 443
    tsm pending-changes apply

    "gateway.public.base_url" might be redundant but I had a bug once with Site Saml so I set it every time now.

Write a comment...
0/9000
Ciara Brennan
Nov 8, 2024, 11:11 AM

💙 Please share your ideas for Tableau Server in the Idea Exchange

💙 Please share your ideas for Tableau Server in the Idea ExchangeIf you haven't already created a Trailblazer ID, please do so using the same email used for your Tableau Forums account.If you haven't already created a Trailblazer ID, please do so using the same email used for your Tableau Forums account.

To create a new idea, go to https://ideas.salesforce.com/s/post and use the Tableau Server category.Tableau Server

ideas.salesforce.com

1 comment
Write a comment...
0/9000
Ciara Brennan
Apr 17, 2024, 1:34 PM

Tableau Server & Cloud Admin User Group | Apr-18-2024 | RSVP here

Permission Deep Dive - Row Level Security

Tableau Server & Cloud Admin User Group | Apr-18-2024 | RSVP herePermission Deep Dive - Row Level Security 

Write a comment...
0/9000
Mauro Pasi
Mar 15, 2024, 1:28 PM
Identity Workbooks with embedded credentials to Published Data source

Hi everyone.

 

I am doing some clean up and want to change ownership of workbook away from people who are no longer at my company.

 

To make it easier for my users I want to move as many workbooks as possible programmatically, without affecting anybody. In order to do this I am trying to identify which workbooks are safe to change and which aren't, using all the tools at my disposal (UI, Repository, Metadata API, REST API).

 

I am able to see which workbook have embedded datasources with passwords (they would be ofc affected) but I can't find a way to identity which of the workbooks that connect to publish datasources do so by embedding the credentials to the datasource as opposed to relying on the user's permissions to connect to the datasource.

 

To make it clearer, I am not referring to embedded database credentials but datasource credentials that allow the user to consume the report without having access to the datasource to begin with: https://help.tableau.com/current/pro/desktop/en-us/publishing_sharing_authentication.htm#workbook-connections-to-tableau-data-sources

 

Are you aware of a way of seeing this? Not even the UI is helpful in distinguishing between the two.

 

Thank you for any help.

1 answer
Write an answer...
0/9000
Raju Dommaraju
Mar 19, 2024, 5:26 PM
Tableau Cloud Monitoring Dashboards.

Hello All,

 

We recently migrated our tableau servers to Tableau Cloud. Looking for any Admin dashboards that will help in cloud administration other than Admin Insights dashboard.

1 answer
Write an answer...
0/9000
Ciara Brennan
Feb 15, 2024, 2:20 PM

Tableau Server & Cloud Admin User Group | Feb-20-2024

RSVP here

Tableau Server & Cloud Admin User Group | Feb-20-2024RSVP here

Write a comment...
0/9000