[SERVER-2750] assertion failed whe using pymongo find_and_modify on sharded db Created: 12/Mar/11 Updated: 30/Mar/12 Resolved: 13/Mar/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 1.7.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | ofer samocha | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | Linux |
| Participants: |
| Description |
|
when using my sharded cluster of mongo I've got this error. Traceback (most recent call last): , variables ) , remove=True) , remove: true }', assertionCode |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 13/Mar/11 ] |
|
No, retry is not safe in the general case as it depends on exaclty when/where things fail. |
| Comment by ofer samocha [ 13/Mar/11 ] |
|
can you implement retry mechanism in mongos ? |
| Comment by Eliot Horowitz (Inactive) [ 13/Mar/11 ] |
|
Seems to be networking issue |
| Comment by Eliot Horowitz (Inactive) [ 13/Mar/11 ] |
|
That looks like a networking blip, not something we could fix. The reason I would upgrade is that 1.7.5 is part of the ubstable series, so 1.8.0-rc2 is more stable |
| Comment by ofer samocha [ 12/Mar/11 ] |
|
mongos side claimed for socket closed. amdbm006 claimed for end connection: was that fixed in 1.8.0 rc2 ? |
| Comment by Eliot Horowitz (Inactive) [ 12/Mar/11 ] |
|
Can you check amdbm006? Also, I would recommend upgrading to 1.8.0-rc2 asap |