Skip to main content

How to install and configure Tableau Server Linux HA | Centos | Redhat |...




















PREPARATION
# Node
information
node1IP:
node2IP:
node3IP:

# TS
installer download


Step1:
Install Initial node

Step 2:
Generate bootstrap file on the initial node
tsm
topology nodes get-bootstrap-file --file <path\file>.json

scp
./bootstrap.json dpark@node2IP:~/
scp
./bootstrap.json dpark@node3IP:~/

Step 3:
Firewall Settings
Step 3-1:
Initial node Firewall settings

1. confirm gateway and tabadmincontroller port number(by default
8850)

tsm topology list-ports | grep -E "tabadmincontroller:primary |
gateway"

2. Check dynamic port range. typical range
is 8000 to 9000.

tsm configuration get -k ports.range.min
  tsm configuration get -k ports.range.max

3. Start firewalld:
  sudo systemctl start firewalld

4. Verify that the default zone is a high-security zone, such
as public.
firewall-cmd --get-default-zone

if change is needed,
sudo firewall-cmd --set-default-zone=public

5. Add ports for the gateway, tabadmincontroller port
and  port range (27000-27010) for  licensing communication between nodes

sudo firewall-cmd --permanent --add-port=80/tcp
  sudo firewall-cmd --permanent
--add-port=27000-27010/tcp

6. Configure the firewall to allow all traffic from the other nodes
in the cluster.

sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4
source address=node2IP/32 port port=8000-9000 protocol=tcp accept'

sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4
source address=node3IP/32 port port=8000-9000 protocol=tcp accept'

7. Reload the firewall and verify the settings.
sudo
firewall-cmd --reload
firewall-cmd
--list-all

Step 3-2:
additional nodes firewall setting

1. Start firewalld:
sudo
systemctl start firewalld

2. Verify that the default zone is a high-security zone, such
as public.
firewall-cmd
--get-default-zone

if change is needed,
sudo firewall-cmd --set-default-zone=public

3. Configure the firewall to
allow gateway and tabadmincontroller access from the other
nodes in the cluster.

on node 2:
sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4
source address=node1IP/32 port port=80 protocol=tcp accept'
sudo
firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source
address=node1IP/32 port port=8000-9000 protocol=tcp accept'

sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4
source address=node3IP/32 port port=80 protocol=tcp accept'
sudo
firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source
address=node3IP/32 port port=8000-9000 protocol=tcp accept'

on node 3:
sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4
source address=node1IP/32 port port=80 protocol=tcp accept'
sudo
firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source
address=node1IP/32 port port=8000-9000 protocol=tcp accept'

sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4
source address=node2IP/32 port port=80 protocol=tcp accept'
sudo
firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source
address=node2IP/32 port port=8000-9000 protocol=tcp accept'


4. Reload the firewall and verify the settings.
sudo
firewall-cmd --reload
firewall-cmd
--list-all

Step 4:
Install Additional node with bootstrap

sudo yum
install tableau-server-version.x86_64.rpm

Step 5:
run initialize-tsm script

cd
/opt/tableau/tableau_server/packages/scripts.<version_code>/
sudo
./initialize-tsm -b /path/to/<bootstrap>.json --accepteula

Repeat
Step4 and 5 on third node.

Step 6:
Add process to the additional nodes.
On
initial node,
tsm
topology set-process -n node2 -pr clustercontroller -c 1
tsm
topology set-process -n node3 -pr clustercontroller -c 1
tsm
pending-changes apply --ignore-warnings

Step 7:
deploy coordination service
tsm stop

##check
if there is any pending list.
tsm
pending-changes list

tsm
pending-changes discard
or
tsm
pending-changes apply

# check
node name
tsm
topology list-nodes -v

#create
coordination service
tsm
topology deploy-coordination-service -n node1,node2,node3
tsm start

Step 8:
Configure Client File Service(CFS)
On
initial node

tsm
topology set-process -n node2 -pr clientfileservice -c 1
tsm
topology set-process -n node3 -pr clientfileservice -c 1

tsm
pending-changes apply


Step
9:  Configure process for second node

tsm
topology set-process -n node2 -pr gateway -c 1
tsm
topology set-process -n node2 -pr vizqlserver -c 2
tsm
topology set-process -n node2 -pr vizportal -c 2
tsm
topology set-process -n node2 -pr backgrounder -c 2
tsm
topology set-process -n node2 -pr cacheserver -c 2
tsm
topology set-process -n node2 -pr searchserver -c 1
tsm
topology set-process -n node2 -pr dataserver -c 2
tsm
topology set-process -n node2 -pr filestore -c 1
tsm
topology set-process -n node2 -pr pgsql -c 1

tsm
pending-changes apply

Step 10:
Configure process for third node

tsm
topology set-process -n node3 -pr gateway -c 1
tsm
topology set-process -n node3 -pr vizqlserver -c 2
tsm
topology set-process -n node3 -pr vizportal -c 2
tsm
topology set-process -n node3 -pr backgrounder -c 2
tsm
topology set-process -n node3 -pr cacheserver -c 2
tsm
topology set-process -n node3 -pr searchserver -c 1
tsm
topology set-process -n node3 -pr dataserver -c 2
tsm
topology set-process -n node3 -pr filestore -c 1

tsm
pending-changes apply

tsm start

Comments

Popular posts from this blog

How to configure LDAPS, LDAP over SSL, using CA Certificate Service on Domain Controller in Windows Server 2016

This post is to provide an instruction on how to set up LDAPS (LDAP over SSL) on Domain Controller using single-tier CA hierachy. Reasons for Enabling LDAPS By default, LDAP communications between client and server applications are not encrypted. This means that it would be possible to use a network monitoring device or software and view the communications traveling between LDAP client and server computers. This is especially problematic when an LDAP simple bind is used because credentials (username and password) is passed over the network unencrypted. This could quickly lead to the compromise of credentials.  Reasons for enabling Lightweight Directory Access Protocol (LDAP) over Secure Sockets Layer (SSL) / Transport Layer Security (TLS) also known as LDAPS include: Some applications authenticate with Active Directory Domain Services (AD DS) through simple BIND. As simple BIND exposes the users’ credentials in clear text, use of Kerberos is preferred. If simp...

Upgrade ESXi server 6.0 to 6.5 using ISO usb

Please note that this is tested with standalone ESXi server 6.0 to upgrade to 6.5. for vCenter users, vCenter 6.5 must be upgraded before upgrade each ESXi host. Preparation It is good idea for you to have a review on follow docs during preparation for the upgrade. 1.  VMware vSphere 6.5 Release notes 2.  KB article about VMware update sequence for vSphere 6.5 and compatible VMware product 3.  Important information before upgrading to vSphere 6.5 Prerequisite 1. Download VMWare vSphere Hypervisor (ESXi) offline bundle ISO file from  vmware download page . 2. Create USB stick with bootable ISO of ESXi 6.5 upgrade. => I am using  rufus tool  to create bootable USB stick. This is free software. How to do steps 1. Reboot ESXi server and change boot order to USB first 2. You will be directed to installation process. -> select disk with ESXi 6.9 installed on . ->  Select Upgrade option and OK -> Once it's done reboot syst...

Solution to Windows Virtual Machine in VMWARE which has set up with 8 vCPU only showing only 2 core.

[Problem] Windows Virtual Machine in  VMWARE   which has set up with 8 vCPU only shows 2 core.  [Instruction] Power off the virtual machine. In Virtual Hardware, Enter the number of CPUs. (ex. 8) Click the VM  Options  tab. in the Advanced options section,  Click Edit Configuration in Configuration Parameters. Add  cpuid.coresPerSocket  in the  Name  column. Enter a value (try 2, 4, or 8) in the  Value  column. (ex. 4) Note : Ensure that the number of vCPUs is divisible by the number of    cpuid.coresPerSocket  in the virtual machine. That is, when you divide the number of vCPUs by the number of  cpuid.coresPerSocket , it must return an integer value. For example,  if your virtual machine is created with 8 vCPUs, coresPerSocket   can only be 1, 2, 4, or 8.