Title
Create new category
Edit page index title
Edit category
Edit link
Deploy TSDB Service on a Separate Node
TSDB contains information related to real-time telemetry events from platform infrastructure, JMX events, and Spark executor or driver JVM usage timeline.
The TSDB standalone installation gives you the choice of running a single TSDB instance that hosts both systems and Spark Graphite Metrics Data events or running two distinct TSDB instances on the same or different hosts.
Follow the steps to make the TSDB a required option.
Single Standalone TSDB
Follow the steps as performed earlier with Install Pulse on Single Node (Docker/Podman-Based).
Run the following commands on the host that is being used for standalone TSDB.
Type the active cluster name, and select FS Elastic.
Login to the Pulse server and open the main Pulse configuration file present at
_ACCELO_HOME/config/acceldata_cluster_name.conf_. Update the influx hostname in every placeholder:
Login to the influx host and connect to Influx db shell for creating databases for SYS, Kafka, Spark, DB names to be used as specified on above Pulse app configuration file.
Login to Pulse core server for updating all Pulse agents to new TSDB, update influx hostname on override.yml file.
On Pulse-core server run the following command to apply the configuration changes.
Run the push config command on Pulse core server to push the updated config changes in application config file. Press Y on any prompts.
Restart all the Pulse services.
For additional help, contact www.acceldata.force.com OR call our service desk +1 844 9433282
Copyright © 2026