[SERVER-13414] profiling can throw stale config after write Created: 31/Mar/14 Updated: 10/Dec/14 Resolved: 31/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Write Ops |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Greg Studer |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Because profiling takes a context for the namespace of the operation and write commands do not use setShardVersion, it's possible for a write to be successful but profiling to throw a stale config error. This aborts the rest of the batch. Issue probably exists in previous versions of mongodb when the database lock of a write is released before profiling, but would require a version change during that interval in order to manifest. |
| Comments |
| Comment by Daniel Pasette (Inactive) [ 31/Mar/14 ] |
|
duplicate: |