top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Can we increase wiredTigerCacheSizeGB value dynamically (at run time) with MangoDB?

+1 vote

We are running MongoDB 3.0 with wiredTiger storage engine and wiredTigerCacheSizeGB is 24.
Now, I want to increase the wiredTigerCacheSizeGB value from 24 to 32. Is it possible to increase this variable without restart the service ?

posted Jun 22, 2015 by anonymous

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button

Similar Questions
+1 vote

In cluster environment, we have two shards (i.e primary, secondary and arbiter servers in each shard).

We have 64GB RAM and wiredTigerCacheSizeGB is currently 32 (by default). Here I need your advise, these serevers are dedicated to Mongo instances.

Can I change to wiredTigerCacheSizeGB to 50GB (leaving 14GB for OS and other processeses).

+1 vote

Is there any impact of running VM if i increase size of VM ?

+1 vote

We Have a 3 node mongodb setup with a primary,secondary and an arbiter. If a Primary node goes down the election process to choose a new primary is taking around 30 seconds. During this period all the Create and Update operations fail. So is there anyway to reduce this failover time so that the client application can resume normal operations in less time.

What is the ideal way to handle Create and Update failures during the failover time? Should it be queued and retried? if the number of operations are high the queue size will not be enough. So please suggest a solution for this problem.If the failover time can be reduced it would solve this problem.

We tried reducing the heartbeat interval in the replica configuration. It did not help either