[SERVER-25938] ShardLocal::runCommand variants should parse writeConcernError even when the command failed Created: 01/Sep/16  Updated: 25/Jan/17  Resolved: 02/Sep/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.3.14

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Spencer Brody (Inactive)
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 2016-09-19
Participants:

 Description   

It is completely valid for commands to both fail and also have a write concern error. ShardRemote already handles this correctly, ShardLocal needs to be updated to behave the same as ShardRemote.

This leads to the following weird error appearing on config servers:

2016-09-01T17:09:00.740-0400 I SHARDING [conn21] couldn't create config.changelog collection: :: caused by :: InternalError: Invalid to check for write concern error if command failed



 Comments   
Comment by Githook User [ 02/Sep/16 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-25938 ShardLocal::runCommand should parse writeConcernError even when the command failed
Branch: master
https://github.com/mongodb/mongo/commit/aa7411e6e2c4fd18bbff934c57567d89dc3efa0e

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