GitHub user 2shar-p added a comment to the discussion: EDW and Data marts
The primary instances and mirror instances will also apply the same way as data distribution - it works across all objects/relations managed by the Cloudberry database. And to be specific about primary:mirror, the mirror as the name suggests just mirrors the data using WAL replication and is quietly standing by until the primary instance fails. It will not be queryable until primary segment becomes unavailable and fault tolerant system marks the primary down and make the mirror available for use. e.g. IF you have 4 segments and a table with 40 rows, ideally you would have evenly distributed data making it 10 rows of data in each of the 4 segments... let's call it p1 thru p4. Now you want to make sure the mirror of these m1 thru m4 are on different physical nodes so if/when there is an issue with underlying infrastructure/hardware, the mirrors running on stable servers will become active and the Cloudberry database stays available without downtime. Hope this helps. GitHub link: https://github.com/apache/cloudberry/discussions/987#discussioncomment-12457759 ---- This is an automatically sent email for dev@cloudberry.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@cloudberry.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cloudberry.apache.org For additional commands, e-mail: dev-h...@cloudberry.apache.org
