Book Image

PostgreSQL 12 High Availability Cookbook - Third Edition

By : Shaun Thomas
Book Image

PostgreSQL 12 High Availability Cookbook - Third Edition

By: Shaun Thomas

Overview of this book

Databases are nothing without the data they store. In the event of an outage or technical catastrophe, immediate recovery is essential. This updated edition ensures that you will learn the important concepts related to node architecture design, as well as techniques such as using repmgr for failover automation. From cluster layout and hardware selection to software stacks and horizontal scalability, this PostgreSQL cookbook will help you build a PostgreSQL cluster that will survive crashes, resist data corruption, and grow smoothly with customer demand. You’ll start by understanding how to plan a PostgreSQL database architecture that is resistant to outages and scalable, as it is the scaffolding on which everything rests. With the bedrock established, you'll cover the topics that PostgreSQL database administrators need to know to manage a highly available cluster. This includes configuration, troubleshooting, monitoring and alerting, backups through proxies, failover automation, and other considerations that are essential for a healthy PostgreSQL cluster. Later, you’ll learn to use multi-master replication to maximize server availability. Later chapters will guide you through managing major version upgrades without downtime. By the end of this book, you’ll have learned how to build an efficient and adaptive PostgreSQL 12 database cluster.
Table of Contents (17 chapters)

Installing and configuring InfluxDB

One critical component of a monitoring system is a data collection or aggregation layer. A very common design here is to use a client-server model so that multiple independent metric gathering services communicate with a centralized system for processing and interpretation.

InfluxDB is a time-series database designed specifically for efficiently ingesting performance metrics from varying sources. One of these just happens to be Telegraf, which we introduced in previous recipes. A common Telegraf + InfluxDB cluster may look like this, with InfluxDB running on a single monitoring server, as seen in this familiar diagram:

InfluxDB acts as a data-gathering and centralization repository so data visualization tools and trend analysis software can produce trend information, graphs, dashboards, alerts, and other useful elements for server management...