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) |
2
(1) |
3
|
4
|
5
|
6
|
7
|
8
(1) |
9
(1) |
10
|
11
|
12
(1) |
13
(5) |
14
|
15
|
16
|
17
|
18
|
19
|
20
|
21
|
22
(4) |
23
(10) |
24
|
25
|
26
|
27
|
28
|
29
|
30
|
31
|
|
From: Masaki H. <his...@la...> - 2013-05-08 05:45:59
|
Hi, Koichi-san, > Could you open bug tickets in sourceforge and assign them to me? ID: 3612883 Rgds, Hisada > -----Original Message----- > From: 鈴木 幸市 [mailto:ko...@in...] > Sent: Wednesday, May 01, 2013 9:51 AM > To: Masaki HISADA > Cc: pos...@li... > Subject: Re: [Postgres-xc-general] GTM standby behaivor when cannot connect > with GTM active > > I have also observed connection error message in gtm slave although there're > no network failure and gtm master is running. We should look into it. > > Also failure to stop gtm standby could be a bug. > > Could you open bug tickets in sourceforge and assign them to me? > --- > Koichi Suzuki > > > > On 2013/04/30, at 16:04, Masaki HISADA <his...@la...> wrote: > > > Hi Kohichi-san, > > > > > >> At present, gtm_standby does not use tcp_keepalives. Gtm_standby just > > wait > >> for GTM to send backups and does not detect network fault until the > >> kernel timeout (usually 60min or so). > > > > From gtm.log, it seems that gtm_standby detecting connection failure > > with GTM about 1 minute after starting up gtm_standby. > > > >>> $ less gtm/data/gtm.log > >>> 1:140357722076928:2013-02-25 04:38:23.850 JST -LOG: Connecting the > >>> GTM active on 192.168.2.1:19000... > >>> LOCATION: gtm_standby_connectToActiveGTM, gtm_standby.c:511 > >>> 1:140357722076928:2013-02-25 04:39:26.856 JST -FATAL: Failed to > >>> establish a connection to active-GTM. > >>> LOCATION: main, main.c:553 > > > >> Because it continues to wait for incoming backup commands, status > >> will > > return > >> that it's running. If Gtm slave starts during the network fault, it > > cannot > >> get initial response from master and it will fail. > > > > I have tried stop immediate in this situation but could not stop > > gtm_standby but cannot stop gtm_standby .... > > Although gtm_standby is waiting for GTM backup, I guess gtm_standby > > needs to be shutting down when immediate shutdown. > > > >> (4) Stop gtm_stadby > > > > $ gtm_ctl -D gtm/data/ -Z gtm start > > server starting > > $ gtm_ctl -D gtm/data/ -Z gtm stop -m immediate waiting for server to > > shut down................ > > ............................................... failed > > gtm_ctl: server does not shut down > > > > Regards, > > > > Mark > > > > > >> Regards; > >> --- > >> Koichi Suzuki > >> > >> > >> > >> On 2013/04/26, at 16:00, Masaki HISADA <his...@la...> > > wrote: > >> > >>> Hi, > >>> > >>> I have been testing pgxc behavior when network between gtm and > >>> gtm_standy has down. > >>> > >>> I have started up gtm_standby and linked down bw gtm and gtm_standby > >>> by using iptables. I expected that gtm_standby would fail with error > >>> because gtm_standby cannot establish synchronization with gtm active. > >>> > >>> Problem : > >>> 1. gtm_standby started without error response although gtm_standby > >>> has failed to establish connection with gtm active from gtm.log. Is > >>> gtm alive or not? > >>> 2. Assuming gtm alive I have tried immediate stop to gtm_standby but > > failed. > >>> 3. Checking at gtm status, it is stopped. > >>> > >>> Question > >>> (1) Am I testing right? > >>> (2) Is this expected behavior for gtm_standby when it cannot > >>> establish connection with gtm? > >>> > >>> Test procedure as follows; > >>> > >>> (1) Start up GTM active at Server A > >>> $ gtm_ctl -D gtm/data/ -Z gtm status > >>> > >>> (2) Network down (simulated with setting iptables) $ iptables -I > >>> INPUT -i bond1 -j DROP $ iptables -I OUTPUT -o bond1 -j DROP > >>> > >>> (3) Start up GTM standby at Server B $ gtm_ctl -D gtm/data/ -Z gtm > >>> start server starting > >>> > >>> (4) Stop gtm_stadby > >>> waiting for server to shut down................ > >>> ............................................... failed > >>> gtm_ctl: server does not shut down > >>> > >>> (5) Check status > >>> $ gtm_ctl -D gtm/data/ -Z gtm status > >>> gtm_ctl: no server running > >>> $ ps aux | grep gtm | grep -v grep > >>> # No output > >>> $ ll gtm/data/ > >>> 合計 12 > >>> -rw------- 1 pgxc pgxc 2217 2月 15 06:15 2013 gtm.conf > >>> -rw------- 1 pgxc pgxc 295 2月 25 04:39 2013 gtm.log > >>> -rw------- 1 pgxc pgxc 45 2月 25 04:38 2013 gtm.pid > >>> > >>> $ less gtm/data/gtm.log > >>> 1:140357722076928:2013-02-25 04:38:23.850 JST -LOG: Connecting the > >>> GTM active on 192.168.2.1:19000... > >>> LOCATION: gtm_standby_connectToActiveGTM, gtm_standby.c:511 > >>> 1:140357722076928:2013-02-25 04:39:26.856 JST -FATAL: Failed to > >>> establish a connection to active-GTM. > >>> LOCATION: main, main.c:553 > >>> > >>> pos...@li... > >>> > >>> Tested Version : commitID(3f15aef4ed3f8b2014d42bce3ed75650c4db907d) > >>> > >>> Rgds, > >>> > >>> Mark > >>> > >>> > >>> -------------------------------------------------------------------- > >>> -- > >>> -------- Try New Relic Now & We'll Send You this Cool Shirt New > >>> Relic is the only SaaS-based application performance monitoring > >>> service that delivers powerful full stack analytics. Optimize and > >>> monitor your browser, app, & servers with just a few lines of code. > >>> Try New Relic and get this awesome Nerd Life shirt! > >>> http://p.sf.net/sfu/newrelic_d2d_apr > >>> _______________________________________________ > >>> Postgres-xc-general mailing list > >>> Pos...@li... > >>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > >>> > >> > >> > >> --------------------------------------------------------------------- > >> ---- > >> ----- > >> Introducing AppDynamics Lite, a free troubleshooting tool for > >> Java/.NET > > Get > >> 100% visibility into your production application - at no cost. > >> Code-level diagnostics for performance bottlenecks with <2% overhead > > Download > >> for free and get started troubleshooting in minutes. > >> http://p.sf.net/sfu/appdyn_d2d_ap1 > >> _______________________________________________ > >> Postgres-xc-general mailing list > >> Pos...@li... > >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > > > > > > > ------------------------------------------------------------------------- > ----- > Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get > 100% visibility into your production application - at no cost. > Code-level diagnostics for performance bottlenecks with <2% overhead Download > for free and get started troubleshooting in minutes. > http://p.sf.net/sfu/appdyn_d2d_ap1 > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general |