[SERVER-6639] getLastError to Mongos gives an empty errmsg field if it fails Created: 30/Jul/12 Updated: 10/Dec/14 Resolved: 04/Apr/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Sharding |
| Affects Version/s: | 2.0.6, 2.2.0-rc0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aristarkh Zagorodnikov | Assignee: | Randolph Tan |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | mongos, replicaset, sharding | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
We were performing a series of restarts of config servers and shards. While some of the servers were rebooting, mongos that used them occasionally returned the following error: { "ok" : 0.0, "errmsg" : "" }). |
| Comments |
| Comment by Randolph Tan [ 08/Aug/12 ] |
|
Bug reproduced - attaching the test file. |
| Comment by Aristarkh Zagorodnikov [ 08/Aug/12 ] |
|
Sure. It was inserting an object into a GridFS chunk collection though mongos (via MongoGridFS.Upload() method of the C# driver), so it was doing something like db.fs.chunks.insert({_id:ObjectId("..."), files_id:NumberLong(...), n:<number>, data:BinData(0,"...")}); |
| Comment by Randolph Tan [ 07/Aug/12 ] |
|
Hi, I have trouble trying to reproduce this. Would you be able to give us more details on what the client was running (I assumed that it was a command) when it got the empty errmsg? Thanks! |
| Comment by Aristarkh Zagorodnikov [ 31/Jul/12 ] |
|
No exact steps, but killing the shard replica set servers leads to this. Wed Jul 25 10:44:08 [WriteBackListener-d2.s2.fs.drive.bru:27022] Socket recv() errno:104 Connection reset by peer 10.3.2.13:27022 Wed Jul 25 10:44:10 [Balancer] Socket recv() errno:104 Connection reset by peer 10.3.2.13:27022 Wed Jul 25 10:44:17 [ReplicaSetMonitorWatcher] Socket recv() errno:104 Connection reset by peer 10.3.2.13:27022 The client got the "empty" error around 10:44:10. |
| Comment by Randolph Tan [ 30/Jul/12 ] |
|
Hi, Do you have the exact steps for reproducing this blank error message? |
| Comment by Aristarkh Zagorodnikov [ 30/Jul/12 ] |
|
First, there is a batch of "can't initialize cursor across all shards" w/socket exceptions interleaved with ReplicaSetMonitor complaining about no master in the replica set. |
| Comment by Aristarkh Zagorodnikov [ 30/Jul/12 ] |
|
That would be too easy =) |
| Comment by Daniel Pasette (Inactive) [ 30/Jul/12 ] |
|
Is there a corresponding error in the mongos log? |