--On Friday, January 21, 2022 9:47 AM +0200 skeletor <[email protected]>
wrote:
I mean that records are present on master, present at accesslog but not
present on slave. Below, what exactly I mean:
- master
reqMod: entryCSN:+ 20220119115618.595929Z#000000#000#000000
reqMod: entryCSN:+ 20220119134148.182859Z#000000#000#000000
reqMod: entryCSN:+ 20220119135935.992674Z#000000#000#000000
reqMod: entryCSN:+ 20220119140414.357271Z#000000#000#000000
- accesslog
reqMod: entryCSN:+ 20220119115618.595929Z#000000#000#000000
reqMod: entryCSN:+ 20220119134148.182859Z#000000#000#000000
reqMod: entryCSN:+ 20220119135935.992674Z#000000#000#000000
reqMod: entryCSN:+ 20220119140414.357271Z#000000#000#000000
- slave
reqMod: entryCSN:+ 20220119115618.595929Z#000000#000#000000
reqMod: entryCSN:+ 20220119140414.357271Z#000000#000#000000
Slave doesn't have 2 middle transactions.
It's a development evronment with a several (about 10-15 of all) records,
so, the MDB maxsize wasn't reached.
In this case I simulated different problems which can cause in
production: network errors between master/slave, restart master, restart
slave. So, i did next
- restarted master and after added a data
- restarted slave and after added a data
- was closed and after added and after opened connections by firewall
You first would need to examine the logs with "stats sync" both enabled and
see what happened when that particular contextCSN was replicated. Perhaps
you have a configuration error or other problem. Without log information
it's impossible to tell what happened in your case.
--Quanah
