couchdb icon indicating copy to clipboard operation
couchdb copied to clipboard

Seamless multi-master syncing database with an intuitive HTTP/JSON API, designed for reliability

Results 231 couchdb issues
Sort by recently updated
recently updated
newest added

## Description In a partitioned DB using custom reduce function doesn't work, all queries to that view fail with 500 error. Creating exact same view in non-partitioned db works. Built...

bug
beginner-friendly
partitioned-db

## Summary Right now it seems that even if I'm sending a valid JWT along with a POST /_session request, CouchDB still requires a user name in the body in...

enhancement
feature
not a bug

Hi Team, We have a 3 node cluster with couch version 3.2.1 deployed on k8s cluster. The db was working working totally fine for about 4-6 weeks, post which, we...

bug
needs-triage

Would it be possible to add support seq_interval on continuous feeds?

enhancement
needs-triage

Hi, ## Description I'm starting three identical CouchDB databases as Docker containers, without data. Same username/admin, same Erlang cookie, same secret. Only the hostname changes. I followed cluster setup instructions....

bug
waiting on user
needs-triage

## Description I am bringing this discussion from the CouchDB slack channel and it's still to be decided whether it's really a bug. So, I started a database replication of...

bug
needs-triage

## Description When I setup a replication to or from our server on my localhost, it fails with the following message in the logs: ``` TLS client: In state hello...

enhancement
waiting on user

## Description There is a bug on main right now where the _users DB cannot be recreated once it has been deleted, and the cluster is rendered completely inoperable until...

bug
waiting on user
cant-reproduce

There's a number of things going on, but a high level summary is that opening a database handle has the possibility of returning `{error, all_dbs_active}`, unfortunately, there are a number...

bug
needs-triage

Hi team, i have a 3 node couch cluster deployed on kubernetes, replication is set in a way like A-B, B-A, B-C, C-B, A-C, C-A using replicator, with continuous replication...

bug
needs-triage