Oh!
We would love to have a reproducible way for this bug 
we have a chaos pipeline, but not always can create this cases.
So after reindexing, you didn’t have this issue anymore, right?
This could be an index corruption. We are working on mitigating this kind of issue with some async read/repair operations.
Let us know if you face any other issues so we can help you on this journey 
Thanks!