As part of the rename flow for sharded collections, the primary shard will issue on the CSRS a transaction enclosing the following operations:

• Update config.collections entry: change nss and epoch (it is actually needed to delete/recreate the document since the namespace is saved in the immutable _id field).
• Update config.chunks entries: change epoch/timestamp (no need to consider the nss field: it's thrown out under SERVER_53105 and rename will just happen with stable FCV)