public inbox for [email protected]
help / color / mirror / Atom feedFrom: [email protected] <[email protected]>
To: Amit Kapila <[email protected]>
To: Fabrice Chapuis <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: RE: Logical replication timeout problem
Date: Fri, 12 Nov 2021 09:22:11 +0000
Message-ID: <OS0PR01MB6113AAC410AA16C5C3D894EBFB959@OS0PR01MB6113.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <CAA4eK1LBN3vqjo=6LVO_FXPJJzEMaNGRSf5E6USmVx4cpab=5w@mail.gmail.com>
References: <CAA5-nLARN7-3SLU_QUxfy510pmrYK6JJb=bk3hcgemAM_pAv+w@mail.gmail.com>
<CAA4eK1JLerufRV4Zr4h-vW4Fjz6LJjd-QZxVywpFrtfvZhXVWg@mail.gmail.com>
<CAA5-nLC0NKo1VsKgf+jEEH=5jGAN2pyCivyG59yX3bQcLSL4tg@mail.gmail.com>
<CAA4eK1KHQfnhmdnLZQrRoAW3dYOPqXKtT5C54HoBno3MCtH4wA@mail.gmail.com>
<CAA5-nLCH-XbCknSx2nVMtCByj8pv3jyRFQxL0qj4FLwby4TyNg@mail.gmail.com>
<CAA4eK1KrJP=oMOu5VJKn1uZjn+Xq110AGUxJpBrp3jN7vWXVPg@mail.gmail.com>
<CAA5-nLA8C0LZdVDdPDNeWcJYGzGVV3nJ7Ni0PdSyHJNxi628ww@mail.gmail.com>
<CAA4eK1LeN1V85i2ZfU2cOj5vJjpEVSvJ6LOfAu-u7mfQrW=v1Q@mail.gmail.com>
<CAA5-nLDhnKRwsPF8z5+ej4D9P9WTfVuMeVsigxuO=+sjf0ruyQ@mail.gmail.com>
<CAA4eK1JYB2eLNTs48szQ8oJXW9GLcrxT0yWETQS0gF2sVBxMYA@mail.gmail.com>
<CAA5-nLCs+XwLma7KPo_GJTKnhXU2YcTD9igMC8uDJV76xk72zQ@mail.gmail.com>
<CAA4eK1JxqfG3v3+E3i=iO5eNK9R8qH_XjZe=POEnW1pRkJ287Q@mail.gmail.com>
<CAA5-nLBPuCJuzAFWnp9ogLT769GsZgH4zTdnXaiUXZh4E3LHSg@mail.gmail.com>
<CAA4eK1Ji-1xCBhwK_obYNmsp5Jv0eCyzeuOqPbOMmkm0Y4K4fw@mail.gmail.com>
<CAA5-nLCw26ih437yHnwg7NJxQ5LULVCXzF7_PwF3a0E2OYz58Q@mail.gmail.com>
<OS0PR01MB6113B93996BBA24F3B066474FBAA9@OS0PR01MB6113.jpnprd01.prod.outlook.com>
<CAA5-nLAVrBZtZ_o-tzbyizFOP3d9mAiG3XUOskShDW01ewfMgw@mail.gmail.com>
<CAA5-nLABf97QKAR8K8NiQs2s6_323dvd7kpAdJ3GZ+p2iR5K7A@mail.gmail.com>
<CAA4eK1LBN3vqjo=6LVO_FXPJJzEMaNGRSf5E6USmVx4cpab=5w@mail.gmail.com>
On Friday, November 12, 2021 2:24 PM Amit Kapila <[email protected]> wrote:
>
> On Thu, Nov 11, 2021 at 11:15 PM Fabrice Chapuis
> <[email protected]> wrote:
> >
> > Hello,
> > Our lab is ready now. Amit, I compile Postgres 10.18 with your patch.Tang, I
> used your script to configure logical replication between 2 databases and to
> generate 10 million entries in an unreplicated foo table. On a standalone instance
> no error message appears in log.
> > I activate the physical replication between 2 nodes, and I got following error:
> >
> > 2021-11-10 10:49:12.297 CET [12126] LOG: attempt to send keep alive
> message
> > 2021-11-10 10:49:12.297 CET [12126] STATEMENT: START_REPLICATION
> 0/3000000 TIMELINE 1
> > 2021-11-10 10:49:15.127 CET [12064] FATAL: terminating logical replication
> worker due to administrator command
> > 2021-11-10 10:49:15.127 CET [12036] LOG: worker process: logical replication
> worker for subscription 16413 (PID 12064) exited with exit code 1
> > 2021-11-10 10:49:15.155 CET [12126] LOG: attempt to send keep alive
> message
> >
> > This message look like strange because no admin command have been executed
> during data load.
> > I did not find any error related to the timeout.
> > The message coming from the modification made with the patch comes back all
> the time: attempt to send keep alive message. But there is no "sent keep alive
> message".
> >
> > Why logical replication worker exit when physical replication is configured?
> >
>
> I am also not sure why that happened may be due to
> max_worker_processes reaching its limit. This can happen because it
> seems you configured both publisher and subscriber in the same
> cluster. Tang, did you also see the same problem?
>
No.
I used the default max_worker_processes value, ran logical replication and
physical replication at the same time. I also changed the data in table on
publisher. But didn't see the same problem.
Regards
Tang
view thread (56+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: RE: Logical replication timeout problem
In-Reply-To: <OS0PR01MB6113AAC410AA16C5C3D894EBFB959@OS0PR01MB6113.jpnprd01.prod.outlook.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox