ReplSet configuration exists on many other members of that replica set. You can safely drop the local db collections (you can even drop the whole DB but then you will just end up syncing from another replica and there is no point to repairing this entire DB). So drop the troublesome collection - it will be recreated when the host rejoins its replica set. The only local collection you need to keep will be the oplog.rs collection - this would allow this member to know where to start catching up for operations it misses while you are doing repairs.
"bytes currently in the cache" : 6009288998 (5.5 GB), "maximum bytes
The number of bytes currently in wiredTiger cache.
configured" : 7516192768 (7 GB),
Maximum size cache is configured (by default half of physical memory on the server).
"bytes read into cache" : 18380155206 (17 GB),
Cumulative number of bytes that have been read into the cache since startup.
"bytes written from cache" : 17020204785 (16 GB),
Cumulative number of bytes that have been written out of the cache into files on disk since startup.
bulk update on DB3 with 23000 update command
You ran a single command with 23K update operations in it, so you were seeing the results you should have expected - you can see in the mongostat output that commands are constantly running and that you always have active writer.
If you actually want high throughput you should use multiple threads to send the operations in parallel to allow use of all cores on the machine.
see dirty% is getting increased continuously
That shows that in fact the writes are happening - higher and higher percentage of the cache is being written to (dirtied). When a checkpoint starts running, the dirty percentage will go down signifying that data from the cache is being persisted to disk (but of course, it's also been written already into write-ahead-log aka journal at the time of original write).
does compression of index also reduces RAM requirement
Yes, indexes are prefix-compressed and the format is the same on disk and in RAM.
Best Answer
As per
github dukku-mongodb
documentation by@josegonzalez
here I don't think the export is actually a tar. The readme we have is wrong, but if you rundokku mongo:help export
, you'll see the correct usage.Here's what
dokku mongo:help export
says:For further your ref here