[SERVER-24827] ShardRemote does not notify the ReplicaSetMonitor on write concern failures Created: 28/Jun/16  Updated: 19/Jul/16  Resolved: 28/Jun/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.3.9
Fix Version/s: 3.3.10

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 17 (07/15/16)
Participants:

 Description   

The ShardRemote::_runCommand does not notify the replica set monitor for write concern errors, which causes the RSM to return the same host over and over again and never attempting to discover a new primary.

This makes the auto-retry logic for config server commands not reliable and causes failures in the sharding continuous stepdown suite.



 Comments   
Comment by Githook User [ 28/Jun/16 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-24827 Notify ReplicaSetMonitor on write concern errors
Branch: master
https://github.com/mongodb/mongo/commit/81b3d4e1c11f5af4e542fbe3baecadc9eebcca45

Generated at Thu Feb 08 04:07:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.