Message-ID: <ac62a1ce2074aff1f4161d30fbbd12b8fe8a1bf5.camel@cybertec.at>
Subject: Re: Replication failed
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Sreejith P <sreejith@lifetrenz.com>, "pgsql-admin@lists.postgresql.org"
	 <pgsql-admin@lists.postgresql.org>
Date: Fri, 18 Dec 2020 12:55:34 +0100
In-Reply-To: 
 <PS2PR02MB2837F275523C57499D567C97F3C30@PS2PR02MB2837.apcprd02.prod.outlook.com>
References: <E73F4CFB-E322-461E-B1EC-82FAA808FEE6@lifetrenz.com>
	 <9492f3e4fff86b6fcb1d064d680920e8579d9c37.camel@cybertec.at>
	 <PS2PR02MB2837F275523C57499D567C97F3C30@PS2PR02MB2837.apcprd02.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk

> > On Fri, 2020-12-18 at 00:56 +0530, Sreejith P wrote:
> > > We had 1 M x 4 slave server streaming replication using Postgres 10. Was working successfully for long time.
> > > 
> > > Suddenly all replication servers got failed and getting following message.
> > > 
> > > 2020-12-17 22:24:32 +04 [1587]: [357-1] db=,user=LOG:  invalid contrecord length 2722 at AEA/A1FFF9E0.
> > > 
> > > Requesting help for identifying root cause.
> >
> > Looks like this problem:
> > https://postgr.es/m/77734732-44A4-4209-8C2F-3AF36C9D4D18%40amazon.com
> >
> > Was there a crash on the primary sever?
> >
> > There is a patch under development at this thread:
> > https://postgr.es/m/CBDDFA01-6E40-46BB-9F98-9340F4379505%40amazon.com
> 
> There was a crash.
> 
> Master recovered automatically .. But replication failed.

Then I am pretty sure that this is the same problem.

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com