On the Replication page, at any time, you can change which namespaces are replicated with the tenant and, if allowed by the tenant configuration, specify whether those namespaces allow erasure coding. If you disable replication for a namespace that was already being replicated, replication of that namespace stops. If you subsequently enable replication for that namespace again, replication of the namespace starts again from where it stopped.
When you reenable replication of a namespace that has already been replicated, all operations that occurred in that namespace while replication was not happening, including object deletions, are replicated to the other system. During this replication, conflicts can occur between changes made on different systems while the namespace was not being replicated.
If you disable replication for a namespace that has already been replicated and then delete the namespace on one or more systems, the namespace deletions are not replicated. If you then reenable replication for that namespace and the namespace still exists on one or more systems, the namespace is replicated back to the systems where you deleted it.
You can also enable or disable replication for a namespace and specify whether the namespace allows erasure coding on the namespace Replication panel.
Depending on the current status of replication, if the tenant is being replicated, you may not be able to disable replication for namespaces that are being replicated.
Allowing erasure coding for a namespace that has shredding enabled as the default for new objects can significantly increase the load on all systems in the replication topology.