News for hackers. Stuff that matters.

A comment on Monitoring your own infrastructure using Grafana, InfluxDB, and CollectD. Parent comment

Re:Monitoring your own infrastructure using Grafana, InfluxD... by didip on Tuesday July 21, 2020 @03:37PM (#23910134)
How does multi node works with Postgres? Does TimescaleDB create its own Raft layer on top and just treat Postgres as dumb storage?
[ Parent | on HN ]
Re:Monitoring your own infrastructure using Grafana, InfluxD... by k-rus on Tuesday July 21, 2020 @04:07PM (#23910438)
A TimescaleDB engineer here. Current implementation of database distribution in TimescaleDB is centralised where all traffics go through an access node, which distributes the load into data nodes. The implementation uses 2PC. Abilities of PostgreSQL to generate distributed query plans are utilised together with TimescaleDB optimisations. So PostgreSQL is used not just a dumb storage :)
[ Parent | on HN ]
Re:Monitoring your own infrastructure using Grafana, InfluxD... by didip on Tuesday July 21, 2020 @05:49PM (#23911353)
Won't that access node be a single point of failure then? Just trying to learn more.
[ Parent | on HN ]
Re:Monitoring your own infrastructure using Grafana, InfluxD... by cevian on Tuesday July 21, 2020 @06:31PM (#23911674)
The access node is replicated using streaming replication and is thus not a SPOF.
[ Parent | on HN ]