[SERVER-3652] Sometimes got "invalid chunk config minObj" or "Assertion: 8070:couldn't find a chunk aftry retry which should be impossible extracted" when there're multiple mongos Created: 19/Aug/11 Updated: 11/Dec/18 Resolved: 02/Nov/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying, Sharding |
| Affects Version/s: | 1.8.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Edward Wei | Assignee: | Scott Hernandez (Inactive) |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | mongos | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Centos 5 64bit |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
I am using a sharding environment(replicaset) with multiple mongos. Sometimes when I perform query or findAndModify a collection with shardkey, there's only ONE mongos worked well, while the others will complains as below. The only way is to restart all the other mongos to fix it. However it may happen again. Query: Aug 19 07:09:56 dal-tsa04 0x5204fa: 0x618f45 0x63a673 0x66841c 0x67d187 0x580b7c 0x6a50a0 0x35baa0673d 0x35b9ed3f6d FindAndModify: Aug 19 07:10:00 dal-tsa04 Fri: Aug 19 07:10:00 [conn60177] Assertion: 8070:couldn't find a chunk aftry retry which should be impossible extracted: { id: "david" }Aug 19 07:10:00 dal-tsa04 0x5204fa: 0x60adfd 0x65663c 0x57df0c 0x635f52 0x66841c 0x67d187 0x580b7c 0x6a50a0 0x35baa0673d 0x35b9ed3f6d |
| Comments |
| Comment by Edward Wei [ 01/Nov/11 ] |
|
@Ian, I've not seen these kind of errors again, maybe I had connection issue at that time. I would suggest close this case first, thank you for help. |
| Comment by Ian Whalen (Inactive) [ 31/Oct/11 ] |
|
@edward, have you seen the same errors again? If so it would be useful if you could attach the logs. |
| Comment by Edward Wei [ 23/Aug/11 ] |
|
@Scott, |
| Comment by Scott Hernandez (Inactive) [ 19/Aug/11 ] |
|
Are all your config servers up and running? Please attach more of the mongos logs before the errors. If you can enable more verbose logging that would help as well. |