[pgpool-hackers: 2294] Re: pgpool-hackers Digest, Vol 66, Issue 43

Tatsuo Ishii ishii at sraoss.co.jp
Thu Apr 27 08:03:41 JST 2017 

Usama,

I have assigned bug 306 to you. It would be nice if you could fix and
get it into 3.6.3.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp

>> would it be possible to postpone the release 3.6.3? Recently I discovered a bug in watchdog and not reliable failover (http://www.pgpool.net/mantisbt/view.php?id=306).
> 
> Sorry, the announcement has been already in public and we can't change
> it.
> 
> Best regards,
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese:http://www.sraoss.co.jp
> 
>> The problem results in incorrect resolving of split brain if the Master Ppgool was disconnected from the majority of pgpool nodes. Later when it gets reconnected again after network connectivity is restored it steals back the Master status from the newly elected Master.
>> 
>> 
>> The problem was detected in the current 3.6.2 version and rarely reproduced in the HEAD of V3_6_STABLE. Also I could detect that in V3_6_STABLE failover sometimes is not initiated.
>> 
>> 
>> Sergey.
>> ________________________________
>> From: Sergey Kim
>> Sent: Tuesday, April 25, 2017 6:05 PM
>> To: Tatsuo Ishii
>> Cc: pgpool-hackers at pgpool.net; Alexander Andreev; Boris Voskanov; Sergey Onuchin
>> Subject: Re: [pgpool-hackers: 2283] Re: pgpool-hackers Digest, Vol 66, Issue 43
>> 
>> 
>> Tatsuo,
>> 
>> 
>>>> ...and do you have any plans to include any code logic related changes into its current state?
>>>I'm not sure what you mean by "related changes"... We will just wrap
>>>the head of V3_6_STABLE branch to create 3.6.3.
>> 
>> 
>> Ok, thank you for the answer, this is what I wanted to know. I was wondering about any possible changes that you probably would like to include into current state of V3_6_STABLE branch.
>> 
>> 
>> Sergey
>> ________________________________
>> From: Tatsuo Ishii <ishii at sraoss.co.jp>
>> Sent: Tuesday, April 25, 2017 5:20 PM
>> To: Sergey Kim
>> Cc: pgpool-hackers at pgpool.net; Alexander Andreev; Boris Voskanov; Sergey Onuchin
>> Subject: Re: [pgpool-hackers: 2283] Re: pgpool-hackers Digest, Vol 66, Issue 43
>> 
>>> Hi Pgpool Community,
>>>
>>>
>>> Of what branch the V3.6.3 will be built from? => Will it be the current V3_6_STABLE branch?
>> 
>> Yes.
>> 
>>> ...and do you have any plans to include any code logic related changes into its current state?
>> 
>> I'm not sure what you mean by "related changes"... We will just wrap
>> the head of V3_6_STABLE branch to create 3.6.3.
>> 
>> Best regards,
>> --
>> Tatsuo Ishii
>> SRA OSS, Inc. Japan
>> English: http://www.sraoss.co.jp/index_en.php
>> Japanese:http://www.sraoss.co.jp
>> 
>>>> The Pgpool-II developement group will make minor releases on Friday,
>>>> April 28.
>>>> Release versions are as follows:
>>>> 3.6.3
>>>> 3.5.7
>>>> 3.4.11
>>>> 3.3.15
>>>> 3.2.20
>>>
>>> Sergey.
>>> ________________________________
>>> From: pgpool-hackers-bounces at pgpool.net <pgpool-hackers-bounces at pgpool.net> on behalf of pgpool-hackers-request at pgpool.net <pgpool-hackers-request at pgpool.net>
>>> Sent: Tuesday, April 25, 2017 6:00 AM
>>> To: pgpool-hackers at pgpool.net
>>> Subject: pgpool-hackers Digest, Vol 66, Issue 43
>>>
>>> Send pgpool-hackers mailing list submissions to
>>>         pgpool-hackers at pgpool.net
>>>
>>> To subscribe or unsubscribe via the World Wide Web, visit
>>>         http://www.sraoss.jp/mailman/listinfo/pgpool-hackers
>>> or, via email, send a message with subject or body 'help' to
>>>         pgpool-hackers-request at pgpool.net
>>>
>>> You can reach the person managing the list at
>>>         pgpool-hackers-owner at pgpool.net
>>>
>>> When replying, please edit your Subject line so it is more specific
>>> than "Re: Contents of pgpool-hackers digest..."
>>>
>>>
>>> Today's Topics:
>>>
>>>    1. [pgpool-hackers: 2279] Pgpool-II minor releases (Tatsuo Ishii)
>>>    2. [pgpool-hackers: 2280] Inifinite retrying to connect to
>>>       backend (Tatsuo Ishii)
>>>
>>>
>>> ----------------------------------------------------------------------
>>>
>>> Message: 1
>>> Date: Tue, 25 Apr 2017 10:13:50 +0900 (JST)
>>> From: Tatsuo Ishii <ishii at sraoss.co.jp>
>>> To: pgpool-hackers at pgpool.net, pgpool-general at pgpool.net
>>> Subject: [pgpool-hackers: 2279] Pgpool-II minor releases
>>> Message-ID: <20170425.101350.1214214673270602254.t-ishii at sraoss.co.jp>
>>> Content-Type: Text/Plain; charset=us-ascii
>>>
>>> Hi all,
>>>
>>> The Pgpool-II developement group will make minor releases on Friday,
>>> April 28.
>>>
>>> Release versions are as follows:
>>>
>>> 3.6.3
>>> 3.5.7
>>> 3.4.11
>>> 3.3.15
>>> 3.2.20
>>>
>>> Best regards,
>>> --
>>> Tatsuo Ishii
>>> SRA OSS, Inc. Japan
>>> English: http://www.sraoss.co.jp/index_en.php
>> SRA OSS, Inc. Japan<http://www.sraoss.co.jp/index_en.php>
>> www.sraoss.co.jp
>> We, SRA OSS, Inc., as a total solution supplier of open source software, provide consulting, software support and training services, as well as supply the PostgreSQL ...
>> 
>> 
>> 
>>> Japanese:http://www.sraoss.co.jp
>>>
>>>
>>> ------------------------------
>>>
>>> Message: 2
>>> Date: Tue, 25 Apr 2017 10:30:40 +0900 (JST)
>>> From: Tatsuo Ishii <ishii at sraoss.co.jp>
>>> To: pgpool-hackers at pgpool.net
>>> Subject: [pgpool-hackers: 2280] Inifinite retrying to connect to
>>>         backend
>>> Message-ID: <20170425.103040.2240088650450323667.t-ishii at sraoss.co.jp>
>>> Content-Type: Text/Plain; charset=us-ascii
>>>
>>> Currently connect_with_timeout() performs infinite retry to connect to
>>> backend if "retry" parameter of the function is true. This happens
>>> when a client connects to Pgpool-II and there's no connection cache
>>> for the request.
>>>
>>> 2017-04-25 09:54:50: pid 9379: LOG:  trying connecting to PostgreSQL server on "133.137.175.105:11003" by INET socket
>>> 2017-04-25 09:54:50: pid 9379: DETAIL:  timed out. retrying...
>>> 2017-04-25 09:54:50: pid 9379: LOCATION:  pool_connection_pool.c:623
>>> 2017-04-25 09:55:00: pid 9379: LOG:  trying connecting to PostgreSQL server on "133.137.175.105:11003" by INET socket
>>> 2017-04-25 09:55:00: pid 9379: DETAIL:  timed out. retrying...
>>> 2017-04-25 09:55:00: pid 9379: LOCATION:  pool_connection_pool.c:623
>>> 2017-04-25 09:55:10: pid 9379: LOG:  trying connecting to PostgreSQL server on "133.137.175.105:11003" by INET socket
>>> :
>>> :
>>>
>>> This continues until health check detects the unavailability of the
>>> backend. Note that if health check is disabled, it continues
>>> forever. Maybe we should have separate configuration parameter from
>>> health check to prevent the infinite retrying?
>>>
>>> Comments?
>>> --
>>> Tatsuo Ishii
>>> SRA OSS, Inc. Japan
>>> English: http://www.sraoss.co.jp/index_en.php
>> SRA OSS, Inc. Japan<http://www.sraoss.co.jp/index_en.php>
>> www.sraoss.co.jp
>> We, SRA OSS, Inc., as a total solution supplier of open source software, provide consulting, software support and training services, as well as supply the PostgreSQL ...
>> 
>> 
>> 
>>> Japanese:http://www.sraoss.co.jp
>>>
>>>
>>> ------------------------------
>>>
>>> _______________________________________________
>>> pgpool-hackers mailing list
>>> pgpool-hackers at pgpool.net
>>> http://www.pgpool.net/mailman/listinfo/pgpool-hackers
>>> pgpool-hackers Info Page<http://www.pgpool.net/mailman/listinfo/pgpool-hackers>
>>> www.pgpool.net<http://www.pgpool.net>
>>> To see the collection of prior postings to the list, visit the pgpool-hackers Archives. Using pgpool-hackers: To post a message to all the list ...
>>>
>>>
>>>
>>>
>>>
>>> End of pgpool-hackers Digest, Vol 66, Issue 43
>>> **********************************************
> _______________________________________________
> pgpool-hackers mailing list
> pgpool-hackers at pgpool.net
> http://www.pgpool.net/mailman/listinfo/pgpool-hackers

More information about the pgpool-hackers mailing list