Standalone TSDB

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

  1. Follow the steps as performed earlier with Install Pulse on a Single Node (Docker).
  2. Run the following commands on the host that is being used for standalone TSDB.
Bash
Copy

Type the active cluster name, and select FS Elastic.

  1. 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:
Bash
Copy
  1. 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.
  2. Login to Pulse core server for updating all Pulse agents to new TSDB, update influx hostname on override.yml file.
Bash
Copy
  1. On Pulse-core server run the following command to apply the configuration changes.
Bash
Copy
  1. Run the push config command on Pulse core server to push the updated config changes in application config file. Press Y on any prompts.
Bash
Copy
  1. Restart all the Pulse services.
Bash
Copy
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard