diff options
| author |   Yanis Guenane <yanis.guenane@enovance.com> | 2015-07-13 09:12:51 +0200 |
|---|---|---|
| committer |   Yanis Guenane <yguenane@redhat.com> | 2015-07-13 10:29:38 +0200 |
| commit | e0ed4b315a5e12703a1e1dfc538863425e6ab81e (patch) | |
| tree | 74ae70984e81c2c220e67b540f2a044c83834d4f /puppet/hieradata | |
| parent | b7400f95a4c185c6c1b3294c11af828d799939d0 (diff) | |
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: I0e4e65af9f650c10fdf5155ff709b4eb984cf4e1
Closes-bug: #1468246
Diffstat (limited to 'puppet/hieradata')
| -rw-r--r-- | puppet/hieradata/controller.yaml | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/puppet/hieradata/controller.yaml b/puppet/hieradata/controller.yaml index 72c10c26..3cc64971 100644 --- a/puppet/hieradata/controller.yaml +++ b/puppet/hieradata/controller.yaml @@ -22,6 +22,7 @@ rabbitmq_config_variables: cluster_partition_handling: 'pause_minority' mongodb::server::replset: tripleo +mongodb::server::journal: false redis::port: 6379 redis::sentinel::master_name: "%{hiera('bootstrap_nodeid')}" |