You can subscribe to this list here.
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
(6) |
Sep
|
Oct
(19) |
Nov
(1) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2011 |
Jan
(12) |
Feb
(1) |
Mar
(4) |
Apr
(4) |
May
(32) |
Jun
(12) |
Jul
(11) |
Aug
(1) |
Sep
(6) |
Oct
(3) |
Nov
|
Dec
(10) |
| 2012 |
Jan
(11) |
Feb
(1) |
Mar
(3) |
Apr
(25) |
May
(53) |
Jun
(38) |
Jul
(103) |
Aug
(54) |
Sep
(31) |
Oct
(66) |
Nov
(77) |
Dec
(20) |
| 2013 |
Jan
(91) |
Feb
(86) |
Mar
(103) |
Apr
(107) |
May
(25) |
Jun
(37) |
Jul
(17) |
Aug
(59) |
Sep
(38) |
Oct
(78) |
Nov
(29) |
Dec
(15) |
| 2014 |
Jan
(23) |
Feb
(82) |
Mar
(118) |
Apr
(101) |
May
(103) |
Jun
(45) |
Jul
(6) |
Aug
(10) |
Sep
|
Oct
(32) |
Nov
|
Dec
(9) |
| 2015 |
Jan
(3) |
Feb
(5) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(9) |
Aug
(4) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
1
|
2
|
3
|
4
(1) |
5
(2) |
6
|
7
|
|
8
|
9
|
10
|
11
|
12
(6) |
13
(2) |
14
(1) |
|
15
|
16
(2) |
17
|
18
|
19
(4) |
20
(2) |
21
(1) |
|
22
|
23
(1) |
24
(1) |
25
(1) |
26
|
27
|
28
|
|
29
|
30
(1) |
|
|
|
|
|
|
From: Phil S. <phi...@ne...> - 2012-04-30 20:38:06
|
Hi all ...
After running some some preliminary testing on our postgres-xc dev
sandbox, I've come across some major concerns with High Availability and
Failover. I am hoping someone will be able to provide some insight on
how to set up seamless high-available failover in a postgres-xc environment.
Here are the details:
--------------------
In the postgres-xc dev sandbox, a test table with the default
round-robin distribution was created to test simultaneous DML SQL
running on both db VMs.
With the DML SQL running, the coordinator and datanode on one of the db
VMs was brought down (NB the host was not shut down, just the
postgres-xc processes on the VM). After a very short time (lets say max
of 2 minutes), the DML SQL script running on the current active db VM
started failing with the following error :
ERROR: Failed to get pooled connections
Our application requires 0 single points of failure. If one of the db
VMs goes down, the application needs the ability to automatically detect
this outage and use the remaining active db VMs in the postgres-xc cluster.
Basically, I need to know how to set up the postgres-xc cluster to
enable the applications to continue to run DML SQL when one of the db
VMs goes down. If this is not supported, then what would need to be put
in place to allow for seamless high-available failover for a postgres-xc
cluster.
Thanks in advance,
Phil.
|