Meta Node

    Meta-Nodes are nodes installed with Pigsty, with admin capability and a complete infra set.

    Current node are marked as meta during , populated in the meta group of .

    Pigsty requires at least one meta node per environment. It will be used as a command center for the entire environment. It’s the meta node’s responsibility to keep states, manage configs, launch plays, run tasks, and collect metrics & logs. The infra set is deployed on meta nodes by default: Nginx, Grafana, Prometheus, Alertmanager, NTP, DNS Nameserver, and DCS.

    The meta node can also be reused as a common node, and a PostgreSQL cluster named pg-meta is created by default on the meta. Supporting additional features: CMDB, routine tasks report, extended apps, log analysis & data analysis, etc.

    The sandbox consists of a with 4 nodes. The sandbox is deployed with one set of and 2 database clusters. meta is the meta node, deployed with infra and reused as a regular node, deployed with meta DB cluster pg-meta. node-1, , and node-3 are normal nodes deployed with cluster pg-test.

    The services running on the meta node are shown below.

    Meta Node - 图2

    Usually, one meta node is sufficient for basic usage, two meta nodes can be used as standby backup, and 3 meta nodes can support a minimal meaningful production-grade DCS Servers themselves!

    Pigsty will set DCS Servers on all meta nodes by default for the sake of “Battery-Included”. But it’s meaningless to have more than 3 meta nodes. If you are seeking HA DCS Servies. Using an external DCS Cluster with 3~5 nodes would be more appropriate.

    Meta nodes are configured under all.children.meta.host in the inventory. They will be marked with meta_node: true flag. The node runs will be marked as meta, and multiple meta nodes have to be configured manually, check for example.

    Last modified 2022-06-04: fii en docs batch 2 (61bf601)