[SERVER-2842] Various errors seen when one node dies in a shard. Created: 26/Mar/11 Updated: 08/Mar/13 Resolved: 18/Sep/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 1.8.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Bernie Hackett | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux x86_64 |
||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Repro: 1. Set up two shards, each with one primary, one secondary, and one arbiter. After killing the mongod you may or may not see errors like this: database error: DBClientBase::findOne: transport error: ... These errors are passed back to the client application by mongos. Is this the expected behavior? This was found while trying to reproduce |
| Comments |
| Comment by Bernie Hackett [ 26/Mar/11 ] |
|
One more: database error: not master and slaveok=false |
| Comment by Bernie Hackett [ 26/Mar/11 ] |
|
Another error (as reported by pymongo): db assertion failure, assertion: 'setShardVersion failed! { "errmsg" : "not master", "ok" : 0 }', assertionCode: 10429 |