[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} ) output from sharding script: |
| Comments |
| Comment by auto [ 28/Apr/10 ] |
|
Author: {'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: really fix getLastError in mongos |
| Comment by auto [ 21/Apr/10 ] |
|
Author: {'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: getLAstError works on mongos assert |