Replica set 'm103-repl' not configured correctly - make sure each node is started with a wiredTiger cache size of 0.1 GB

Even after adding below lines in config file of replica m103-repl, above warning coming when validated with validation command of course lab.

vagrant@m103:/var/mongodb/db$ cat mongod-repl-1.conf
sharding:
clusterRole: shardsvr
storage:
wiredTiger:
engineConfig:
cacheSizeGB: 0.1

from db.serverStatus() values:

MongoDB Enterprise m103-repl:SECONDARY> db.serverStatus().wiredTiger.cache
{
“application threads page read from disk to cache count” : 140,
“application threads page read from disk to cache time (usecs)” : 21785,
“application threads page write from cache to disk count” : 187,
“application threads page write from cache to disk time (usecs)” : 105720,
“bytes belonging to page images in the cache” : 242589,
“bytes belonging to the lookaside table in the cache” : 182,
“bytes currently in the cache” : 362051,
“bytes not belonging to page images in the cache” : 119462,
“bytes read into cache” : 2546220,
“bytes written from cache” : 1257466,
“checkpoint blocked page eviction” : 0,
“eviction calls to get a page” : 10,
“eviction calls to get a page found queue empty” : 10,
“eviction calls to get a page found queue empty after locking” : 0,
“eviction currently operating in aggressive mode” : 0,
“eviction empty score” : 0,
“eviction passes of a file” : 0,
“eviction server candidate queue empty when topping up” : 0,
“eviction server candidate queue not empty when topping up” : 0,
“eviction server evicting pages” : 0,
“eviction server slept, because we did not make progress with eviction” : 0,
“eviction server unable to reach eviction goal” : 0,
“eviction state” : 32,
“eviction walk target pages histogram - 0-9” : 0,
“eviction walk target pages histogram - 10-31” : 0,
“eviction walk target pages histogram - 128 and higher” : 0,
“eviction walk target pages histogram - 32-63” : 0,
“eviction walk target pages histogram - 64-128” : 0,
“eviction walks abandoned” : 0,
“eviction walks gave up because they restarted their walk twice” : 0,
“eviction walks gave up because they saw too many pages and found no candidates” : 0,
“eviction walks gave up because they saw too many pages and found too few candidates” : 0,
“eviction walks reached end of tree” : 0,
“eviction walks started from root of tree” : 0,
“eviction walks started from saved location in tree” : 0,
“eviction worker thread active” : 4,
“eviction worker thread created” : 0,
“eviction worker thread evicting pages” : 0,
“eviction worker thread removed” : 0,
“eviction worker thread stable number” : 0,
“failed eviction of pages that exceeded the in-memory maximum count” : 82,
“failed eviction of pages that exceeded the in-memory maximum time (usecs)” : 2066,
“files with active eviction walks” : 0,
“files with new eviction walks started” : 0,
“force re-tuning of eviction workers once in a while” : 0,
“hazard pointer blocked page eviction” : 27,
“hazard pointer check calls” : 189,
“hazard pointer check entries walked” : 544,
“hazard pointer maximum array length” : 3,
“in-memory page passed criteria to be split” : 0,
“in-memory page splits” : 0,
“internal pages evicted” : 28,
“internal pages split during eviction” : 0,
“leaf pages split during eviction” : 0,
“lookaside score” : 0,
“lookaside table entries” : 0,
“lookaside table insert calls” : 0,
“lookaside table remove calls” : 0,
“maximum bytes configured” : 106954752,
“maximum page size at eviction” : 0,

Thanks,
Srinivas

I don’t see a problem with the shown node as 106954752 is closed to .1GB.

http://www.unitconversion.org/unit_converter/data-storage.html

However, there is 2 other mongod processes in m103-repl. They also need to be configured at .1GB.

1 Like

Hi Steeve,

Thanks for your response, Memory allocation has been the same across all nodes of Replication Set m103-repl. Where as when tried to validate the Lab task with given command “validate_lab_first_sharded_cluster
its throwing this warning " [Replica set ‘m103-repl’ not configured correctly - make sure each node is started with a wiredTiger cache size of 0.1 GB]" .

But today when i started my Vagranat box and ran the validate command, it worked fine.

Sometimes course validate commands responds strangely .