Jump to content
KAZOOcon: hackathon signup and details here! ×

Start including CouchDB v2.1


amn

Recommended Posts

CouchDB v2.1 has been released.  

https://github.com/apache/couchdb/releases/tag/2.1.0

I believe there are official RPMs now as well.

http://apache.bintray.com/couchdb-rpm/el7/x86_64/

Seems to work ok with Kazoo v4.1.  Does it make sense to start including couchDB config, systemd, RPM etc. in the Kazoo RPMs?  At least in the experimental branch.

 

Edited by amn (see edit history)
Link to comment
Share on other sites

  • 2600Hz Employees

I think this is a great suggestion! I've been using Couch 2 (well, the master branch that I update every week or so) to good effect. We'll have to wait and see how operations feels about migrating existing installations from BigCouch to Couch 2. I think that's the main holdup at this point.

Would love to hear experiences others have with migrations and with running Couch 2 vs BigCouch.

Link to comment
Share on other sites

  • 2 weeks later...
  • 3 months later...
On 8/7/2017 at 4:59 PM, mc_ said:

I think this is a great suggestion! I've been using Couch 2 (well, the master branch that I update every week or so) to good effect. We'll have to wait and see how operations feels about migrating existing installations from BigCouch to Couch 2. I think that's the main holdup at this point.

Would love to hear experiences others have with migrations and with running Couch 2 vs BigCouch.

I'm running CouchDB 2 in production, and I haven't had any issues. I had the luxury of planning my first deployment around this transition, so I don't have any experience with the migration.

Link to comment
Share on other sites

On 12/18/2017 at 2:44 PM, Tom said:

I'm running CouchDB 2 in production, and I haven't had any issues. I had the luxury of planning my first deployment around this transition, so I don't have any experience with the migration.

I would be interested in your configs that are different from bigcouch.  Looks to be almost the same except for zones.  There is just one comment by the developer with one example but not explained in much detail.

 

Edited by amn (see edit history)
Link to comment
Share on other sites

48 minutes ago, amn said:

I would be interested in your configs that are different from bigcouch.  Looks to be almost the same except for zones.  There is just one comment by the developer about it with one example it but not explained in much detail.

 

These are the only things I changed: https://github.com/kazoo-ansible/couchdb/tree/master/templates

Note: I'm only running in one zone right now.

Edited by Tom (see edit history)
Link to comment
Share on other sites

  • 1 month later...
3 hours ago, cecchisandrone said:

Anyone has successfully set zones? I'm trying to follow http://docs.couchdb.org/en/latest/cluster/databases.html but I don't understand how to modify _nodes database to add zone attribute. Am I wrong?

/nodes is accessed via port 5986 (or 15986 if you are going through HAProxy).

So from a web browser http://CouchDB_IP_Address:5986/nodes to access it via the Fauxton web interface.  That is assuming Fauxton is configured to also access 5986 by default as it is 5984.  I don't have an CouchDB install in front of me to check that. 

If it is locked down you will need to know the user/pass for access.

I believe you can also do it from CURL similar to the examples they give for front end configuration.

Edited by amn (see edit history)
Link to comment
Share on other sites

  • 1 month later...
×
×
  • Create New...