diff options
| author |   Dan Prince <dprince@redhat.com> | 2015-01-10 22:04:42 -0500 |
|---|---|---|
| committer | Dan Prince <dprince@redhat.com> | 2015-01-27 09:07:19 -0500 |
| commit | 25b35cb71174c1db971e2f80b693d1be2e502d4e (patch) | |
| tree | 13a99d07c652b4e68421e8f2b8d7a794815516cf /swift-deploy.yaml | |
| parent | af061f09c68e11ca03a9b63c7183a52782d6cc10 (diff) | |
Swift: set default replicas to 3
Our existing default (replicas == 1) means that no data
(or copies) is being replicated in a multi-node Swift
environment. This seems like a bad production default
setting and could easily slip by if not set.
Setting it to 3 shouldn't hurt anything and seems to follow
suit with what several production installers (based around Puppet)
actually use. If using an installation with less than 3 swift
nodes I believe swift will do its best, and still work fine.
FWIW I noticed this when testing a multi-node Puppet swift
installation and was surprised when I didn't see any *data
files getting replicated across the storage cluster.
Change-Id: I44bdfff7aae6bdf845b79ca1f8f450c22113caed
Diffstat (limited to 'swift-deploy.yaml')
| -rw-r--r-- | swift-deploy.yaml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/swift-deploy.yaml b/swift-deploy.yaml index 1e15511f..d4d32cbd 100644 --- a/swift-deploy.yaml +++ b/swift-deploy.yaml @@ -24,7 +24,7 @@ parameters: hidden: true SwiftReplicas: type: number - default: 1 + default: 3 description: How many replicas to use in the swift rings. resources: controller0Swift: |