[pgpool-general: 5852] Re: pgpool ver. 3.6.6 / problem with restart

[Bo Peng]

Hi,

I think the problem is that Pgpool-II wasn't stopped by using fast mode.
if there are some connections from clients, Pgpool-II will wait until 
all connections exit. This caused that Pgpool-II hangs up.

Pgpool-II should use fast mode to stop and restart.

Could you try to change the /etc/sysconfig/pgpool file like this:

------
- #STOP_OPTS=" -m fast"  
+ STOP_OPTS=" -m fast"  
------

And we also find the problem at pgpoolAdmin that stop mode didn't work correctly.
Could you try the attached patch to pgpoolAdmin.

On Thu, 11 Jan 2018 10:10:30 +0100
Aleksander Englert <aleksander_englert at skg.pl> wrote:

> Thanks for your interest in the matter. The active passive solution is 
> not possible. As for the pgpool reboot, in version 3.2.3 we used the 
> fast option and all connections were closed. Pgpool restarted nicely. So 
> something changed in newer versions?
> 
> 
> W dniu 11.01.2018 o 09:53, Piotr Gbyliczek pisze:
> >
> >
> > 		Piotr Gbyliczek
> > ------------------------------------------------------------------------
> > Solutions Engineer
> > ddi. *08454 210444*
> > t. *0845 123 2222*
> > e. *P.Gbyliczek at node4.co.uk* 	*Nottingham Office*
> > Node4 Ltd, The POD,
> > 10 Bottle Ln, Nottingham, NG1 2HL
> >
> > 	
> > Visit www.node4.co.uk <http://www.node4.co.uk>
> >
> >
> > 	
> > Visit www.node4.co.uk <http://www.node4.co.uk>
> >
> > 		
> > Visit Node4 on Twitter <http://www.twitter.co.uk/Node4Ltd>
> >
> > 		
> > Visit Node4 on Linkedin <https://www.linkedin.com/company/node4-ltd>
> >
> > 		
> > Visit Node4 on Facebook <http://www.facebook.com/Node4>
> >
> > 		
> >
> > <https://www.node4.co.uk/events/how-to-solve-your-database-management-challenge/> 
> >
> >
> > 	
> > <https://www.node4.co.uk/events/leeds-open-day/>
> >
> > On Thursday, 11 January 2018 08:38:44 GMT Aleksander Englert wrote:
> > > Thanks for fast reaction. The problem is that as soon as I connect to
> > > pgpool only with pgadmin, restart is not possible, pgpool is hanging.
> > > When I close the pgadmin, pgpool is then turned off and waits to start.
> > > The entire process path is shown in the following step-by-step
> > > screenshots. Earlier, pgpool version 3.2.3 was used and a similar
> > > problem did not occur. I will just say that the topic is very important
> > > to us, because it is about using pgpool in the application used in the
> > > Ministry of Finance.
> >
> > AFAIK pgpool does wait for connections to be closed on stopping.
> >
> > The timeout that Tatsuo suggested should help with that, but setting 
> > it too
> > low may cause some legitimatelly idle connections being cut off.
> >
> > You can have a look at this (from pgpool --help) :
> >
> > =================
> > Stop options:
> > -m, --mode=SHUTDOWN-MODE
> > Can be "smart", "fast", or "immediate"
> >
> > Shutdown modes are:
> > smart quit after all clients have disconnected
> > fast quit directly, with proper shutdown
> > immediate the same mode as fast
> > =================
> >
> > and set appropriate option in /etc/sysconfig/pgpool or in pgpool.conf 
> > (not
> > sure if that is possible there)
> >
> > Another solution may be to add another pgpool server and use watchdog. 
> > I've
> > seen pgpool hanging on stop all the time, but since we use it normally in
> > active passive pair, watchdog detects that pgpool is stopped and passive
> > pgpool pick ups the active role, thus allowing new connections to go 
> > through
> > to database. I usually wait few minutes on the former active server 
> > and then
> > kill pgppool processes there, then start pgpool back as passive server in
> > pair.
> >
> >
> > Regards,
> > Piotr
> > -- 
> >
> > Node4 Limited is registered in England No: 04759927 and has its 
> > registered office at Millennium Way, Pride Park, Derby, DE24 8HZ
> > The information contained in this email is confidential and is 
> > intended for the exclusive use of the email addressee shown.
> > If you are not the addressee, any disclosure, reproduction, 
> > distribution or other dissemination or use of this communication is 
> > strictly prohibited.
> > If you have received this mail in error, please notify our mail 
> > manager at abuse at node4.co.uk <mailto:abuse at node4.co.uk> and delete it 
> > from your system.
> > Opinions expressed in this email are those of the individual not the 
> > company, unless specifically indicated to that effect.
> > ------------------------------------------------------------------------
> > This email has been scanned by Node4's Email Security System.
> > ------------------------------------------------------------------------
> > This email message has been delivered safely and archived online by 
> > Mimecast.
> >
> >
> >
> > _______________________________________________
> > pgpool-general mailing list
> > pgpool-general at pgpool.net
> > http://www.pgpool.net/mailman/listinfo/pgpool-general
> 
> -- 
> Pozdrawiam / Best regards
> Aleksander Englert
> aleksander_englert at skg.pl
> tel. 33/8281168
> kom. +48692469269
> 
> SKG S.A.
> 43-309 Bielsko-Biała, Al. Armii Krajowej 336
> tel. +48 33 8281-100, fax +48 33 8281-105
> e-mail: firma at skg.pl
> 
> Nr KRS: 47940, Sąd Rejonowy w Bielsku-Białej, VIII Wydział Gospodarczy KRS
> NIP: 547-12-57-936, Regon: 070711270
> Kapitał zakładowy: 500 000 zł w całości opłacony
> 
> Niniejsza wiadomość może zawierać informacje prawnie chronione. 
> Wiadomość skierowana jest wyłącznie do
> adresata/ adresatów określonych wyżej i stanowi własność nadawcy. 
> Odbiorca, który otrzymał tę wiadomość
> przypadkowo, proszony jest o jej nie rozpowszechnianie, a następnie 
> poinformowanie nadawcy i jej
> usunięcie. Rozpowszechnianie, kopiowanie, ujawnianie lub przekazywanie 
> osobom trzecim w jakiejkolwiek
> formie informacji zawartych w niniejszej wiadomości w całości lub części 
> jest zakazane.
> 
> The information contained in this message may be privileged and 
> confidential and protected from disclosure.
> Information included in that message is addressed only to the 
> addressee/addressees determined above and is the property
> of the sender. If you have received this communication in error, please 
> notify the sender immediately by replaying
> to the message and deleting it from your computer. Any dissemination, 
> distribution or copying of this communication
> to the third parties is strictly prohibited.


-- 
Bo Peng <pengbo at sraoss.co.jp>
SRA OSS, Inc. Japan
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: restart.diff
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20180111/a3d35ddb/attachment.ksh>