KNOWLEDGE BASE

Using DSR (Direct Server Return) Load Balancing on Tableau, Ask Data On The Additional Nodes May Fail To Start


Published: 28 Oct 2022
Last Modified Date: 28 Oct 2022

Issue

When using DSR (Direct Server Return) load balancing, Ask Data (nlp) on additional nodes may fail to start.

Environment

  • Tableau Server
  • Multi-Node
  • DSR (Direct Server Return)

Cause

When using DSR (Direct Server Return) load balancing on Tableau Server, if it dynamically adds a virtual IP to the Tableau Server machine, the elasticsearch used by Ask Data (nlp) on additional nodes cannot connect to the initial node correctly.

Additional Information

After running tsm start command, the following error can be found in tabadmincontroller_node1-0.log:

ERROR com.tableausoftware.tabadmin.webapp.asyncjobs.JobStepRunner - Running step StartAllServices failed
com.tableausoftware.tabadmin.webapp.exceptions.ServiceOperationTimeoutException: One or more services failed to reach their expected state.
node2:
    nlp_0.<build number>: Failed to start. Current status: DOWN
node3:
    nlp_0.<build number>: Failed to start. Current status: DOWN


If it's a Linux OS, the following error can be found in system messages (/var/log/messages):

level=info msg="waiting for successful ping to Elasticsearch" error="failed to create es.Client {errorSourceService: Elasticsearch} [client.go:173]: no active connection found: no Elasticsearch node available" retryInterval=100ms
...
nlp_0.service failed

Did this article resolve the issue?