0

I followed an offical document to deploy mongodb to AWS,After the template completed,I found two huge volumes are allocated : enter image description here

After some investigation,I found it hard coded in template file(provided by the guide): enter image description here

And used for journaling:

enter image description here

I am not a dedicated database administrator ,so I want to know what is reason to allocate so huge storage

I want to know if decrease the rate for iops for journalling volume will decrease the overall database performance

Guichi
  • 2,150
  • 1
  • 19
  • 27
  • Unless you actually know that your workload needs that kind of IOPS, I wouldnt use it, its actually rather expensive. – datasage Sep 19 '16 at 05:30
  • @datasage I do not know what is the significance of journal and log in mongodb, if it is irrelevant,I will just reduce the resource for it – Guichi Sep 19 '16 at 05:36
  • Every operation done in Mongo is written to the journal, this is used for replication to other instances in a cluster. You can configure the log to be as detailed as you want it to be. Obviously the more detail you are logging, the more IOPS you will use. – datasage Sep 19 '16 at 05:38
  • Is 25GB necessary ? someone mention the size should be fix and it seems 3GB is the fixed value – Guichi Sep 19 '16 at 05:41
  • Also,is the journalling performance related to external performance ? – Guichi Sep 19 '16 at 05:42
  • 1
    It depends on the size of your data and workload. There is not a good once size fits all solution. If you are asking these questions, you may not be in a place where you need separate volumes for journals and logs. – datasage Sep 19 '16 at 05:42
  • Journaling has to do with replication and crash recovery. But with enough write volume, you can run into IO constraints. – datasage Sep 19 '16 at 05:43

0 Answers0