[
https://issues.apache.org/jira/browse/COUCHDB-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15468251#comment-15468251
]
Chris Foster commented on COUCHDB-2980:
---------------------------------------
Hi everyone,
Just chiming in on this again. Sorry for the delay, don't check JIRA often.
Sounds like you guys have summarized our parallel conclusions.
We also stumbled across using "http://localhost:5984/db"; as a workaround. It's
not perfect, because it essentially means we can not change the port without
having to run some weird migration script. It does ensure we won't accidentally
replicate to production all the time though.
I think part of the confusion for me is that I was coming from 1.X. This worked
really well for us in 1.X because we just did "databaseA" to "databaseB" and
never had to worry about URLs. In 2.X, even though we still aren't using
clustering yet and would prefer to not worry about it right now, it appears
that our databases are still clustered (on one host) and our method of just
specifying the database name was failing in a really confusing way.
As mentioned, this workaround works for us for now so don't let us hold you
back from 2.0, but it would be cool to eventually have a better approach for
this. Although, I am not sure what that might look like :)
> Replicator DB on 15984 replicates to backdoor ports
> ---------------------------------------------------
>
> Key: COUCHDB-2980
> URL: https://issues.apache.org/jira/browse/COUCHDB-2980
> Project: CouchDB
> Issue Type: Bug
> Components: Replication
> Affects Versions: 2.0.0
> Reporter: Robert Kowalski
>
> If you POST a doc into the replicator database a replication is kicked off
> and finishes successfully (usual 5984 port which maps to 15984 via haproxy).
> The problem is that the DB is replicated to the backdoor ports (15986) and is
> not visible on the other ports.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
