Details
-
Bug
-
Resolution: Unresolved
-
Minor
-
7.6.0, 7.0.0-Beta1, 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.1.4, 7.0.5, 7.1.0, 7.1.1, 7.1.2, 7.2.0, 7.1.3, 7.2.1, 7.1.5, 7.2.4, 7.0.6, 7.1.7, 7.2.2, 7.1.6, 7.2.3, 7.2.5, 7.6.2, 7.2.6, 7.6.1, 7.6.4, Cypher, 7.2.7
-
Untriaged
-
0
-
Unknown
Description
The document flags are a 4-byte metadata field that is under control/ownership of the client. Any mutation can set the flags and KV just replicates that around, DCP_MUTATION has a field for flags and XDCR can (and does) sends the flags to remote clusters.
When the document is deleted we get a difference, e.g. couch_dbdump of the active will show the flags are preserved, but replica 0 (and xdcr replicated deletes).
This is because DCP_DELETION has no flags field and that's mostly correct as there's not much a client can do with a tombstone, if they bring it back to life (set again) the client must reset the flags, the server has no functionality to resurrect flags, so we have no issue that the replica has 0 other than 15 minutes head scratching when looking at dbdumps.
The active should zero the flags when creating a delete.