[SERVER-17178] dbhash got out of sync Created: 04/Feb/15 Updated: 22/May/15 Resolved: 22/May/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | David Storch |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
http://buildlogs.mongodb.org/MCI_amazon/builds/660456/test/parallel_compatibility_WT_0/basicPlus.js |
| Comments |
| Comment by David Storch [ 05/Feb/15 ] |
|
From my reading of the code, the dbhash command takes a MODE_S lock on the database. Then it computes a hash for each collection in the database using a non-yielding plan executor. The error in the logs from the WiredTiger integration layer has in the past been a sign that we're not prepared to properly handle writes that become visible in a new WiredTiger snapshot. Since the shared database lock is held for the lifetime of the dbhash operation, however, I'm not sure how there could be any concurrent writes happening in the database. Needs some more digging. |