[pgpool-general: 174] Re: VM nodes marked down after snapshot

Guillaume DOUTE g.doute at linkbynet.com
Wed Jan 18 01:58:28 JST 2012


Thanks for your reply and your explanations,

I can't understand why but I can't reproduce my problem. Things seems quite stable, fortunately. I will reply with logs when I'll encounter the problem again

On a side question : I don't understand however why I keep getting "DEBUG" lines in my logs although I didn't launch pgpool with "-d". Logs are too verbose and get too big, so I can't enable logging all the time. Any particular reasons as to why pgpool behaves this way ?

Thanks again!

____________________________________________________
Guillaume Douté
Administrateur Activités Transversales
----------------------------------------------------
LINKBYNET
Columbia 
32 boulevard Vincent Gâche - 44000 Nantes
Tel direct : +33 (0)2 40 71 61 64
Tel : +33 (0)1 48 13 00 00 - Fax : +33 (0)1 48 13 31 21
Email : g.doute at linkbynet.com - Web : www.linkbynet.com
_____________________________________________________
Astreinte : http://www.linkbynet.com/astreinte/

Avant d'imprimer cet e-mail, pensez à l'environnement.


-----Message d'origine-----
De : Tatsuo Ishii [mailto:ishii at postgresql.org] 
Envoyé : lundi 16 janvier 2012 13:21
À : Guillaume DOUTE
Cc : pgpool-general at pgpool.net
Objet : Re: [pgpool-general: 151] VM nodes marked down after snapshot

I myself never tried pgpool VM but...

Pgpool marks a node "down" even if health check is disabled. If reading or writing socket for PostgreSQL backend on VM fails, pgpool trigger failover and marks it down. You should see error messages in pgpool log. Please check.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp

> I'm using pgpool-II 3.0.4 in an environnement with two postgresql nodes in streaming replication, one of them is a physical machine, the other is a virtual one. I'm experiencing some odd behaviour with the virtual nodes. Every once in a while, when a snapshot is made or when it's deleted, pgpool mark it as "down".
> 
> I tried to tweak abit the health checks parameters but it didn't help. Even after deactivating health check, the node can get marked as down by pgpool.
> The annoying part is that it is not always systematic. Sometimes, the snapshot works fine with no consequences. But I must say that it's rarely the case.
> 
> I've looked around googling anything known with pgpool and vmware but couldn't find anything interesting. Am I the only one experiencing this ?
> 
> ____________________________________________________
> Guillaume Douté
> Administrateur Activités Transversales
> ----------------------------------------------------
> LINKBYNET
> Columbia
> 32 boulevard Vincent Gâche - 44000 Nantes Tel direct : +33 (0)2 40 71 
> 61 64 Tel : +33 (0)1 48 13 00 00 - Fax : +33 (0)1 48 13 31 21 Email : 
> g.doute at linkbynet.com<mailto:g.doute at linkbynet.com> - Web : 
> www.linkbynet.com<http://www.linkbynet.com/>
> _____________________________________________________
> Astreinte : http://www.linkbynet.com/astreinte/
> 
> Avant d'imprimer cet e-mail, pensez à l'environnement.
> 


More information about the pgpool-general mailing list