CDP sync fails after hot add of memory to source vm

[aschmieg]

I have seen a couple of instances that CDP sync fails and won't restart. It occurred same day the memory on the source VM was increased (hot-add).
In both cases had to delete CDP policy and the replica and cleanup files in ESX for the source and replica VM.

From a CDP standpoint is this expected? Should CDP be disabled for the source VM before making hot-add changes to a VM?

If not expected, i will open a support case, once i re-create the problem.