Home > database >  Directing the main library execute mongodump lead to rising of memory
Directing the main library execute mongodump lead to rising of memory

Time:09-29

Mongo 3.4.4 WiredTiger engine
Structure of master-slave replication (Master/Slave)
To start with, the mongod occupies physical memory (res) is 1.8 G, by performing the mongodump - oplog, mongod occupies physical memory up to 3 G, mongo's data is only 1.3 G (1.3 G/data/mongo/data)

Excuse me each great god what reason is this? Even when mongod all the data and index loaded into memory, also should be only 1.3 G?

In addition, is there any way to release the memory?

CodePudding user response:

Wiredtiger snnapy compressed storage see 1.3 G memory would be more

Another masterslave has abandoned this architecture can not automatically switch should use a replicate set

CodePudding user response:

Thank you for your guidance! That excuse me is there a way to release the mongo memory? Under the condition of not restart mongod,

CodePudding user response:

Dump, we should use the admin; Db. FsyncLock () write lock
  • Related