SERVER-77068 Use collection acquisitions in Update/Delete stages

1 files changed, 2 insertions, 6 deletions

diff --git a/src/mongo/db/exec/update_stage.h b/src/mongo/db/exec/update_stage.h
index 9c9bcc483ad..2f7dfd397aa 100644
--- a/src/mongo/db/exec/update_stage.h
+++ b/src/mongo/db/exec/update_stage.h
@@ -85,7 +85,7 @@ private:
  *
  * Callers of doWork() must be holding a write lock.
  */
-class UpdateStage : public RequiresMutableCollectionStage {
+class UpdateStage : public RequiresWritableCollectionStage {
     UpdateStage(const UpdateStage&) = delete;
     UpdateStage& operator=(const UpdateStage&) = delete;
 
@@ -144,9 +144,6 @@ protected:
     mutablebson::Document& _doc;
     mutablebson::DamageVector _damages;
 
-    // Cached collection sharding description. It is reset when restoring from a yield.
-    write_stage_common::CachedShardingDescription _cachedShardingCollectionDescription;
-
 private:
     /**
      * Computes the result of applying mods to the document 'oldObj' at RecordId 'recordId' in
@@ -186,8 +183,7 @@ private:
      * been updated to a value belonging to a chunk that is not owned by this shard. We cannot apply
      * this update atomically.
      */
-    void checkUpdateChangesExistingShardKey(const ShardingWriteRouter& shardingWriteRouter,
-                                            const BSONObj& newObj,
+    void checkUpdateChangesExistingShardKey(const BSONObj& newObj,
                                             const Snapshotted<BSONObj>& oldObj);
 
     void checkUpdateChangesReshardingKey(const ShardingWriteRouter& shardingWriteRouter,