| From: | "MauMau" <maumau307(at)gmail(dot)com> |
|---|---|
| To: | "Ashutosh Bapat" <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
| Cc: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Robert Haas" <robertmhaas(at)gmail(dot)com>, "PostgreSQL Hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: I'd like to discuss scaleout at PGCon |
| Date: | 2018-06-05 16:48:47 |
| Message-ID: | ACCD2FA21E9745C9956A76E0F8D03EAE@tunaPC |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
From: Ashutosh Bapat
> Each node need to be confiugred and maintained. That requires
efforts.
> So we need to keep the number of nodes to a minimum. With a
> coordinator and worker node segregation, we require at least two
nodes
> in a cluster and just that configuration doesn't provide much
> scalability. With each node functioning as coordinator (facing
> clients) and worker (facing other coordinators) keeps the number of
> nodes to a minimum. It is good for HA.
I think so, too. Every node should behave as both the coordinator and
the data node in XL parlance. But I don't preclude a central node.
Some node needs to manage sequences, and it may as well manage the
system catalog.
Regards
MauMau
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James Keener | 2018-06-05 16:51:03 | Re: Code of Conduct plan |
| Previous Message | James Keener | 2018-06-05 16:47:05 | Re: Code of Conduct plan |