This is to avoid the syncing node winding up with an incomplete set of data due to the inability of initial sync to properly handle renameCollection. See SERVER-4941 for more details.
Document that upgrading to 3.2.12 and 3.4.0 may cause initial sync to fail if collection renames are happening
Initial syncing node maintains tmp collection from map reduce when primary has renamed it
collection rename may not replicate / clone properly during initial sync
Provide option to 3.2 and 3.4 to allow initial sync to complete even when it encounters renameCollection entries