By default MongoDB enables a journaling system that prevents loss of
data in case of an unexpected shut-down. When journaling is enabled,
MongoDB will create the journal files before actually starting the
daemon[1].
The journaling feature is useful in production environment, but not
really on a CI-like system, where we only want to make sure MongoDB is
setup correctly and running, hence here we allow a user to
enable/disable MongoDB journaling.
Reviewed: https:/ /review. openstack. org/201025 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=e0ed4b315a5 e12703a1e1dfc53 8863425e6ab81e
Committed: https:/
Submitter: Jenkins
Branch: master
commit e0ed4b315a5e127 03a1e1dfc538863 425e6ab81e
Author: Yanis Guenane <email address hidden>
Date: Mon Jul 13 09:12:51 2015 +0200
Allow a user to disable MongoDB journaling
By default MongoDB enables a journaling system that prevents loss of
data in case of an unexpected shut-down. When journaling is enabled,
MongoDB will create the journal files before actually starting the
daemon[1].
The journaling feature is useful in production environment, but not
really on a CI-like system, where we only want to make sure MongoDB is
setup correctly and running, hence here we allow a user to
enable/disable MongoDB journaling.
[1] http:// docs.mongodb. org/manual/ core/journaling /
Change-Id: I0e4e65af9f650c 10fdf5155ff709b 4eb984cf4e1
Closes-bug: #1468246