MongoDB count results in incorrect number (MongoDB count a pit)

In a MongoDB cluster, if exists orphaned documents and chunk migration, the count query may result in an incorrect query result, such as I was stepping on the pit, first not talking, see the result:

Skip can only get to 54631, and count found out 77,396 data, this is the pit, the same query conditions, not the same results, in order to avoid this result, you can use the aggregate query,

As shown, the inside is a pit.

For more information on the count of MongoDB, see official website: https://docs.mongodb.com/manual/reference/command/count/

MongoDB count results in incorrect number (MongoDB count a pit)