Info
Currently, reconfig cmd does not wrap the no-op oplog write write in a writeConflictRetry block. It's always safe to wrap any writes to a record store in a writeConflictRetry block because writeConflict exception can be thrown in the mongodb layer even for some memory pressure/issues in WiredTiger.
Top User Comments
xgen-internal-githook commented on Wed, 6 Nov 2019 23:24:54 +0000:
Author:
{'username': 'ali-mir', 'email': 'ali.mir@mongodb.com', 'name': 'Ali Mir'}
Message: SERVER-43236 Wrap reconfig cmd no-op oplog write in writeConflictRetry block
(cherry picked from commit 55e80afa2d511b9bd1a316d3fd4cb6185baa829b)
Branch: v3.6
https://github.com/mongodb/mongo/commit/43f4a99347f17c73b9502cba88e4214a28a0005d
xgen-internal-githook commented on Wed, 6 Nov 2019 19:51:53 +0000:
Author:
{'name': 'Ali Mir', 'username': 'ali-mir', 'email': 'ali.mir@mongodb.com'}
Message: SERVER-43236 Wrap reconfig cmd no-op oplog write in writeConflictRetry block
(cherry picked from commit 55e80afa2d511b9bd1a316d3fd4cb6185baa829b)
Branch: v4.0
https://github.com/mongodb/mongo/commit/0d5240e8af0e9aa7c29c45138f6054c761a2a178
xgen-internal-githook commented on Tue, 5 Nov 2019 21:48:53 +0000:
Author:
{'username': 'ali-mir', 'email': 'ali.mir@mongodb.com', 'name': 'Ali Mir'}
Message: SERVER-43236 Wrap reconfig cmd no-op oplog write in writeConflictRetry block
(cherry picked from commit 55e80afa2d511b9bd1a316d3fd4cb6185baa829b)
Branch: v4.2
https://github.com/mongodb/mongo/commit/614a240344fbab759fe1bf83276ae5b68e9ff3ba
xgen-internal-githook commented on Thu, 24 Oct 2019 18:06:54 +0000:
Author:
{'name': 'Ali Mir', 'username': 'ali-mir', 'email': 'ali.mir@mongodb.com'}
Message: SERVER-43236 Wrap reconfig cmd no-op oplog write in writeConflictRetry block
Branch: master
https://github.com/mongodb/mongo/commit/55e80afa2d511b9bd1a316d3fd4cb6185baa829b
