[SERVER-25057] Initial sync fails on 2d index build Created: 14/Jul/16 Updated: 28/Jul/17 Resolved: 25/Aug/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Geo, Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Eric Milkie |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | Repl 18 (08/05/16), Repl 2016-08-29 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
During a patch build of the initial sync passthrough I hit:
When initial sync tries to create the collection, it does not accept this index. |
| Comments |
| Comment by Githook User [ 28/Jul/17 ] | |||||||||||||
|
Author: {'email': 'benety@mongodb.com', 'username': 'benety', 'name': 'Benety Goh'}Message: Revert " This reverts commit ff7f0344468bc7de67f9905a469e2c6f6359e4ac. | |||||||||||||
| Comment by Githook User [ 28/Jul/17 ] | |||||||||||||
|
Author: {'email': 'benety@mongodb.com', 'username': 'benety', 'name': 'Benety Goh'}Message: Revert " This reverts commit 3d313292efac3654393d30e0eb439e3df7728171. | |||||||||||||
| Comment by Githook User [ 28/Jul/17 ] | |||||||||||||
|
Author: {'email': 'benety@mongodb.com', 'username': 'benety', 'name': 'Benety Goh'}Message: | |||||||||||||
| Comment by Githook User [ 28/Jul/17 ] | |||||||||||||
|
Author: {'email': 'benety@mongodb.com', 'username': 'benety', 'name': 'Benety Goh'}Message: | |||||||||||||
| Comment by Eric Milkie [ 08/Aug/16 ] | |||||||||||||
|
| |||||||||||||
| Comment by Judah Schvimer [ 14/Jul/16 ] | |||||||||||||
|
This appears to be a race between the collection clone and getting the first op to apply on the initial sync node. Consider the following order of events:
| |||||||||||||
| Comment by Daniel Pasette (Inactive) [ 14/Jul/16 ] | |||||||||||||
|
it appears from looking at the test that this could only happen if the drop collection command on L32 of jstests/core/multikey_geonear.js did not replicate or was not registered somehow before the createIndex call was made. |