[Email protected] mongodb]# tree/data./data|--Wiredtiger | | --Wiredtiger.lock | | --Wiredtiger.turtle |--engine configuration file |--wiredtiger.wt | |--wiredtigerlas.wt || --_MDB_CATALOG.WT |--metadata information for all collections |--diagnostic.data| |--metrics.2016-07-27t23-37-15z-00000| '--metrics.interim|--journal |--similar to Redo Log| |--wiredtigerlog.0000000001| |--wiredtigerpreplog.0000000001| '--wiredtigerpreplog.0000000002|--local| |--collection-0--3645467719118758283.wt| '--index-1--3645467719118758283.wt|--mongod.lock |--sizestorer.wt |--capacity of all collections Information '--storage.bson3 directories, Files[[email protected] MongoDB] Note_MDB_CATALOG.WT: The metadata of all the collections is stored, including the corresponding WT table name, collection creation option, index information of the collection, etc., when the WT storage engine initializes, it reads all the collection information from the _MDB_CATALOG.WT and loads the meta information into the memory.SIZESTORER.WT: Stores the capacity information for all collections, such as the number of documents, the total size of the document, etc., when inserting, deleting, updating a document, this information is first cache to memory, each operation 1000 times will brush the disk once The Mongod process crash may cause the data in the SIZESTORER.WT to not match the actual information and can be re-scanned by the Validate () command to revise the statistics
MONGODB 3.2 Storage Directory structure description