[COMPASS-3722] Index creation flaky Created: 24/Jun/19 Updated: 27/Oct/23 Resolved: 04/Mar/20 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | Indexes |
| Affects Version/s: | None |
| Fix Version/s: | 1.20.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Massimiliano Marcon | Assignee: | Durran Jordan |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Sprint: | Iteration Ragamuffin, Iteration Snake, Iteration Xerus, Iteration Yak |
| Description |
|
During the keynote at MDBW, we had an issue during the creation of a wildcard index: https://youtu.be/SODvhxJnAcI?t=3003 Here is how I could reproduce it twice and then never again: Compass 1.19:
Then Compass master:
In both cases the index is created. Note that this is not specific to wildcard indexes: other users had errors with regular indexes too. |
| Comments |
| Comment by Asya Kamsky [ 04/Nov/19 ] |
|
The driver should know what server version it’s talking to, right? |
| Comment by Asya Kamsky [ 03/Jul/19 ] |
|
I wonder if it’s some spurious thing that Compass is sending. Note that the error was something about system.indexes which hadn’t been a thing in the server for a while. Also the index was successfully created both times so ... could some extra something be sent after the index was created? |