Re: Repeated requests for feedback in logical standby
От | Magnus Hagander |
---|---|
Тема | Re: Repeated requests for feedback in logical standby |
Дата | |
Msg-id | CABUevEzVcyL_p+Ck10XsK120XszvfBmfhN=LQkh8zvj7=uHYfw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Repeated requests for feedback in logical standby (Magnus Hagander <magnus@hagander.net>) |
Ответы |
Re: Repeated requests for feedback in logical standby
|
Список | pgsql-bugs |
On Thu, Apr 14, 2016 at 12:30 PM, Magnus Hagander <magnus@hagander.net> wrote: > > > On Thu, Apr 14, 2016 at 7:34 AM, Nick Cleaton <nick@cleaton.net> wrote: > >> On 12 April 2016 at 16:18, Magnus Hagander <magnus@hagander.net> wrote: >> > >> > I've been running some tests, and come across a weird behavior on >> shutdown with logical replication, 9.5.2. It seems that on shutdown, a lot >> of extra requests for feedback are sent from the walsender. >> > >> > On my laptop I get about 3-15 requests (different each time), and on a >> server with a bit more power but still very low activity, the number is >> simply huge. >> > >> > Basically what happens is: >> > >> > * Replication works fine >> > * I have *zero* activity on the master since it got started, not even a >> single psql >> > * I issue a fast shutdown on the master >> > * Nothing happens at all for a while >> > * Once pg_recvlogical times out and sends a status message things wake >> up >> > * The server sends a whole bunch of requests for status, which >> pg_recvlogical responds to >> > * Eventually things shut down (on the proper server, I've had to kill >> things because it takes too long - I'm unsure if it ever shuts down) >> >> >> That sounds similar to something I've seen with wal-based replication: >> >> http://www.postgresql.org/message-id/flat/CAFgz3kus=rC_avEgBV=+hRK5HYJ8vXskJRh8yEAbahJGTzF2VQ@mail.gmail.com#CAFgz3kus=rC_avEgBV=+hRK5HYJ8vXskJRh8yEAbahJGTzF2VQ@mail.gmail.com > > > Agreed, that sounds very similar. > > I don't know the code enough to say whether that's a proper fix though, or > if it might have other sideeffects. > > I should add that yes, this patch does seem to remove the problem for me as well. But I can't confirm if it breaks something else. Hopefully someone who has worked more on that code can? I also still see the problem that "pg_ctrl stop -m fast" on the master does *nothing* until the client sends one message. I tried increasing the feedback interval to 2 minutes, and that increased the shutdown time to 2 minutes as well. Which can't be right - clearly the shutdown is failing to actually make the walsender send the request and shut down. This happens both with and without the suggested patch. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/
В списке pgsql-bugs по дате отправления: