[SERVER-2449] potential concurrency issue in repl pairs updateSetsWithLocalOps() if oplog loops over during yield Created: 31/Jan/11 Updated: 01/Feb/11 Resolved: 01/Feb/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
In replica pairs mode, updateSetsWithLocalOps() maintains a list of ops that are not known to have been applied to the peer. In some cases we may do a dbtemprelease in this function or in updateSetsWithOps() which could invalidate a non client cursor and BSONObj if oplog insertions during the dbtemprelease cause the cursor's current pointer to be deleted. This issue is in replica pairs mode only. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 01/Feb/11 ] |
|
replica pairs are going away |