[SERVER-28113] which scene can lead to relocate the document phyisical order Created: 25/Feb/17  Updated: 27/Feb/17  Resolved: 27/Feb/17

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 3.2.11
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: Malie Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

mongodb 3.2.11
centos6.6


Participants:

 Description   

we have a scene that we need traverse the whole collection ,and also record where we traverse to so that we can continue to do it if process failed,
I try update and delete some documents and db.collecton.find() return the same order but I can't find some issue to explain whether it is clustered index about wiredTiger. In MMAP I know it could change the location of data and find() return unordered.
So I want to confirm in wiredtiger whether some operations can lead to db.collection.find() return unordered not include chunk moving in th shard or wiredtiger use clustered index ?



 Comments   
Comment by Kelsey Schubert [ 27/Feb/17 ]

Hi 402309718@qq.com,

Thanks for your report. If sort order is important for your application, I would recommend using an index rather than relying on the $natural sort.

Please note that SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-users group.

Kind regards,
Thomas

Generated at Thu Feb 08 04:17:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.