remove bigcouch docs

3 files changed, 2 insertions, 109 deletions

diff --git a/pages/docs/platform/services/couchdb.md b/pages/docs/platform/services/couchdb.md
index cc40dc3..862ca56 100644
--- a/pages/docs/platform/services/couchdb.md
+++ b/pages/docs/platform/services/couchdb.md
@@ -69,85 +69,6 @@ Beware that this returns the uncompacted disk size (see http://wiki.apache.org/c
 
     echo "`curl --netrc -s -X GET 'http://127.0.0.1:5984/user-dcd6492d74b90967b6b874100b7dbfcf'|json_pp|grep disk_size|cut -d: -f 2`/1024"|bc
 
-
-Deprecated BigCouch Tasks
------------------------------------------
-
-As of release 0.8, the LEAP platform no longer supports BigCouch. This information is kept here for historical reference.
-
-### Rebalance Cluster
-
-Bigcouch currently does not have automatic rebalancing.
-It will probably be added after merging into couchdb.
-If you add a node, or remove one node from the cluster,
-
-1. make sure you have a backup of all DBs !
-
-1. put the webapp into [[maintenance mode => services/webapp#maintenance-mode]]
-
-1. Stop all services that access the database:
-
-    ```
-    workstation$ leap ssh soledad-nodes
-    server# /etc/init.d/soledad-server stop
-
-    workstation$ leap ssh mx-node
-    server# /etc/init.d/postfix stop
-    server# /etc/init.d/leap-mx stop
-
-    workstation$ leap ssh webapp
-    server# /etc/init.d/nickserver stop
-    ```
-
-    Alternately, you can create a temporary firewall rule to block access (run on couchdb server):
-
-    ```
-    server# iptables -A INPUT -p tcp --dport 5984 --jump REJECT
-    ```
-
-1. dump the dbs:
-
-    ```
-    cd /srv/leap/couchdb/scripts
-    time ./couchdb_dumpall.sh
-    ```
-
-1. delete all dbs
-
-1. shut down old node
-
-1. check the couchdb members
-
-    ```
-    curl -s —netrc-file /etc/couchdb/couchdb.netrc -X GET http://127.0.0.1:5986/nodes/_all_docs
-    curl -s —netrc-file /etc/couchdb/couchdb.netrc http://127.0.0.1:5984/_membership
-    ```
-
-1. remove bigcouch from all nodes
-
-    ```
-    apt-get --purge remove bigcouch
-    ```
-
-1. deploy to all couch nodes
-
-    ```
-    leap deploy couchdb
-    ```
-
-1. most likely, deploy will fail because bigcouch will complain about not all nodes beeing connected. Let the deploy finish, restart the bigcouch service on all nodes and re-deploy:
-
-    ```
-    /etc/init.d/bigcouch restart
-    ```
-
-1. restore the backup
-
-    ```
-    cd /srv/leap/couchdb/scripts
-    time ./couchdb_restoreall.sh
-    ```
-
 ### Migrating from BigCouch to plain CouchDB
 
 <%= render :partial => 'docs/platform/common/bigcouch_migration_begin.md' %>
diff --git a/pages/docs/platform/troubleshooting/known-issues.md b/pages/docs/platform/troubleshooting/known-issues.md
index 4defc88..8621521 100644
--- a/pages/docs/platform/troubleshooting/known-issues.md
+++ b/pages/docs/platform/troubleshooting/known-issues.md
@@ -66,15 +66,7 @@ if you see this error, simply restart the node.
 CouchDB
 ---------------------
 
-At the moment, we strongly advise only have one bigcouch server for stability purposes.
-
-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:
-
-    # watch -n1 -d lsof -p `pidof beam`|wc -l
-
-The command `leap db destroy` will not automatically recreate new databases. You must run `leap deploy` afterwards for this.
+At the moment, we only support one couchdb server for stability purposes.
 
 User setup and ssh
 ------------------
diff --git a/pages/docs/platform/troubleshooting/where-to-look.md b/pages/docs/platform/troubleshooting/where-to-look.md
index c92fba8..0869ee2 100644
--- a/pages/docs/platform/troubleshooting/where-to-look.md
+++ b/pages/docs/platform/troubleshooting/where-to-look.md
@@ -98,30 +98,10 @@ Couchdb
 Places to look for errors
 -------------------------
 
-* `/opt/bigcouch/var/log/bigcouch.log`
+* `/var/log/couchdb/couch.log`
 * `/var/log/syslog` (watch out for stunnel issues)
 
 
-
-Bigcouch membership
--------------------
-
-* All nodes configured for the provider should appear here:
-
-<pre>
-    curl -s --netrc-file /etc/couchdb/couchdb.netrc -X GET 'http://127.0.0.1:5986/nodes/_all_docs'
-</pre>
-
-* All configured nodes should show up under "cluster_nodes", and the ones online and communicating with each other should appear under "all_nodes". This example output shows the configured cluster nodes `couch1.bitmask.net` and `couch2.bitmask.net`, but `couch2.bitmask.net` is currently not accessible from `couch1.bitmask.net`
-
-
-<pre>
-    curl -s --netrc-file /etc/couchdb/couchdb.netrc 'http://127.0.0.1:5984/_membership'
-    {"all_nodes":["bigcouch@couch1.bitmask.net"],"cluster_nodes":["bigcouch@couch1.bitmask.net","bigcouch@couch2.bitmask.net"]}
-</pre>
-
-* Sometimes a `/etc/init.d/bigcouch restart` on all nodes is needed, to register new nodes
-
 Databases
 ---------