The ReshardingChangeStreamsMonitor currently creates a DBClientCursor once and use it to consume change stream events until the final event ("reshardBlockingWrites" or "reshardDoneCatchUp"). According to the Service Arch team, it is safer to drop it and reschedule it on every iteration. There have been some scenarios where holding decorations on an OperationContext for a long time and reusing them causes unexpected resource consumption.