[SERVER-25260] ApplyOps needs to check for existing OpObserver Created: 25/Jul/16 Updated: 23/Aug/16 Resolved: 23/Aug/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Jess Fan | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Sprint: | Sharding 18 (08/05/16), Sharding 2016-08-29 |
| Participants: |
| Description |
|
In _applyOps:
is called without checking that getOpObserver != null. Blocking the noDistlock project. |
| Comments |
| Comment by Spencer Brody (Inactive) [ 23/Aug/16 ] |
|
In https://github.com/mongodb/mongo/commit/e38918afa79bbb952e82a5127cb36d85f919703a we added an invariant that the opobserver is non-null |
| Comment by Randolph Tan [ 25/Jul/16 ] |
|
spencer Some of the unit tests are running without the opObserver setup since they don't really need it. |
| Comment by Spencer Brody (Inactive) [ 25/Jul/16 ] |
|
Can getGlobalServiceContext()->getOpObserver() ever return nullptr? |