[SERVER-45718] Index builder can skip index building for a non-empty collections due to incorrect fast count value. Created: 23/Jan/20 Updated: 29/Oct/23 Resolved: 27/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Suganthi Mani | Assignee: | Suganthi Mani |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||
| Sprint: | Execution Team 2020-01-27, Execution Team 2020-02-10 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Linked BF Score: | 86 | ||||||||||||||||||||||||||||
| Description |
|
Currently the fast count gets flushed to WT/disk only during following cases. Basically, fast count is not tolerant to unclean shutdowns. So, if a node containing non-empty collections restarts after an unclean shutdown, there is a possibility that that fast count returned after node restart can be 0 for that non-empty collection. As, a result, index build can skip index building thinking that's an empty collection. |
| Comments |
| Comment by Githook User [ 27/Jan/20 ] |
|
Author: {'username': 'smani87', 'name': 'Suganthi Mani', 'email': 'suganthi.mani@mongodb.com'}Message: |