[SERVER-1039] sharding getLastError only reports mongod error Created: 21/Apr/10  Updated: 12/Jul/16  Resolved: 21/Apr/10

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

Type: Bug Priority: Critical - P2
Reporter: Mathias Stearn Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

> db.foo.insert({_id:1, key:1}
> db.foo.update({_id:1, key:1},

{key:2}

)
> db.getLastErrorObj()

{ "err" : null, "ok" : 1 }

output from sharding script:
S1: Wed Apr 21 18:02:50 UserException: change would move shards!



 Comments   
Comment by auto [ 28/Apr/10 ]

Author:

{'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}

Message: really fix getLastError in mongos SERVER-1039
http://github.com/mongodb/mongo/commit/e0d8e8541d2870a2280c9513ac742b5b1864c766

Comment by auto [ 21/Apr/10 ]

Author:

{'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}

Message: getLAstError works on mongos assert SERVER-1039
http://github.com/mongodb/mongo/commit/c6643c12f64f2b36f4ff591d3282f00b0480fd30

Generated at Thu Feb 08 02:55:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.