diff options
| author | guido <guido@bruo.org> | 2014-05-05 12:26:03 -0400 |
|---|---|---|
| committer | guido <guido@bruo.org> | 2014-05-05 12:26:03 -0400 |
| commit | c48f250df89b961c7a962be0a4dfeac1b42d37f7 (patch) | |
| tree | fed67da5ce153bbf5d716ffc7b04dc85bbcf06bf /docs/platform/known-issues.md | |
| parent | 33fdf642742efe08b6e20d57b07dda39fa6e85d6 (diff) | |
Updated docs to reflect issues of bug #5601
The docs reflect the problem when adding new couchdb nodes after one o
more have been deployed.
Diffstat (limited to 'docs/platform/known-issues.md')
| -rw-r--r-- | docs/platform/known-issues.md | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/platform/known-issues.md b/docs/platform/known-issues.md index 46a77de..5bf41a6 100644 --- a/docs/platform/known-issues.md +++ b/docs/platform/known-issues.md @@ -5,6 +5,13 @@ Here you can find documentation about known issues and potential work-arounds in the current Leap Platform release. +0.5.1 +===== +CouchDB Sync +------------ +You can't deploy new couchdb nodes after one or more have been deployed. Make *sure* that you configure and deploy all your couchdb nodes when starting the provider. The problem is that we dont not have a clean way of adding couch nodes after initial creation of the databases, so any nodes added after result in improperly synchronized data. See Bug [#5601](https://leap.se/code/issues/5601) for more information. + + 0.5.0rc1 ======== |