Problem Description
Records are not getting shipped via XDR, even though it is enabled. The Aerospike logs on the source cluster show
{namespace_name} DC dc_name abandon result 4
and the logs on the destination cluster show the following printing the digest of the record that is unable to get written on the destination node.
{namespace_ name} write_master: can't replace record b2180ad4ced8ba3a9673f59b61f16aa774eed601 if conflict resolving
Explanation
This happens when
conflict-resolve-writes is set to true but bin convergence is not in use. As explained in the
bin convergence documentation , enabling conflict-resolve-writes prevents records from being written via replacement, which is the default write policy for XDR.
Solution
If bin convergence is not being used, there is no need to have conflict-resolve-writes enabled. Dynamically disable it with
asadm -e "enable; manage config namespace namespace_name param conflict-resolve-writes to false"
Applies To Earliest Version
5.4
Applies To Latest Version
Current Version
