diff options
| author | Micah Anderson <micah@riseup.net> | 2015-06-09 15:33:05 -0400 |
|---|---|---|
| committer | Micah Anderson <micah@riseup.net> | 2015-06-09 15:33:35 -0400 |
| commit | f3e84dc75ae72f96da1afd827361eeb8f56955b6 (patch) | |
| tree | 127d195804f967764c892c6c2aee36aa50256a69 /pages/docs/platform/troubleshooting | |
| parent | d22474705a0df20924ac19be554febea0f9d4229 (diff) | |
make it clear that one couch node is all that will really work
Diffstat (limited to 'pages/docs/platform/troubleshooting')
| -rw-r--r-- | pages/docs/platform/troubleshooting/known-issues.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/pages/docs/platform/troubleshooting/known-issues.md b/pages/docs/platform/troubleshooting/known-issues.md index f274462..4defc88 100644 --- a/pages/docs/platform/troubleshooting/known-issues.md +++ b/pages/docs/platform/troubleshooting/known-issues.md @@ -66,9 +66,9 @@ if you see this error, simply restart the node. CouchDB --------------------- -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. +At the moment, we strongly advise only have one bigcouch server for stability purposes. -In some scenarios, such as when certain components are unavailable, the couchdb syncing will be broken. When things are brought back to normal, shortly after restart, the nodes will attempt to resync all their data, and can fail to complete this process because they run out of file descriptors. A symptom of this is the webapp wont allow you to register or login, the /opt/bigcouch/var/log/bigcouch.log is huge with a lot of errors that include (over multiple lines): {error, emfile}}. We have raised the limits for available file descriptors to bigcouch to try and accommodate for this situation, but if you still experience it, you may need to increase your /etc/sv/bigcouch/run ulimit values and restart bigcouch while monitoring the open file descriptors. We hope that in the next platform release, a newer couchdb will be better at handling these resources. +With multiple couch nodes (not recommended at this time), in some scenarios, such as when certain components are unavailable, the couchdb syncing will be broken. When things are brought back to normal, shortly after restart, the nodes will attempt to resync all their data, and can fail to complete this process because they run out of file descriptors. A symptom of this is the webapp wont allow you to register or login, the /opt/bigcouch/var/log/bigcouch.log is huge with a lot of errors that include (over multiple lines): {error, emfile}}. We have raised the limits for available file descriptors to bigcouch to try and accommodate for this situation, but if you still experience it, you may need to increase your /etc/sv/bigcouch/run ulimit values and restart bigcouch while monitoring the open file descriptors. We hope that in the next platform release, a newer couchdb will be better at handling these resources. You can also see the number of file descriptors in use by doing: |