DR fails atomicity in 7.3.43

[doublex]

After updating FDB from 7.3.37 to 7.3.43 the disaster-recovery fails atomicity.

What we did:

fdbdr start --source /path/to/src.cluster --destination /path/to/dst.cluster
[wait until the DR is a complete copy of the primary database]
fdbdr abort --source /path/to/src.cluster --destination /path/to/dst.cluster

Older transactions are fine - but newer transactions are not atomic on the DR-clone.
For example: The secondary-index is there without a primary record.

If I remember correctly this did not happen with 7.3.37.
Is it safe to downgrade FDB to 7.3.37? If so, I could check.

Best wishes

[jzhou77]

Is it safe to downgrade FDB to 7.3.37? If so, I could check.

Yes.

[doublex]

@jzhou77
Thanks. v7.3.37 works perfectly.
I will upgrade sender/recipient up to v7.3.43 to determine the regression.
That's probably all I can contribute.

[doublex]

fdb_dr keeps atomicity if the primary-database ("sender") is not v7.3.43.
v7.3.37 -> v7.3.37: works (transactions are atomic)
v7.3.37 -> v7.3.43: works
v7.3.41 -> v7.3.43: works
v7.3.43 -> v7.3.43: secondary-indexes written, primary records missing (some)

Is there anything I can do to help?