[jira] [Commented] (COUCHDB-2980) Replicator DB on 15984 replicates to backdoor ports

["Chris Foster (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/COUCHDB-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364767#comment-15364767 ] 

Chris Foster commented on COUCHDB-2980:
---------------------------------------

I think we really need a way of not specifying the full URL. We have a series of inter-cluster replications that are continuous and persistent (in the `_replicator` table), and full URL's make that a big pain.

If all of the replication tables are set up to use a full URL, then it becomes impossible to replicate a production database elsewhere. The destination database you replicate the `_replicator` table to immediately starts double replicating the production tables, not its own databases. Since the credentials are included there is no way to stop this without also stopping replication in the production cluster.

Even if there was just a way to say "this cluster", that would be significantly more ideal than hardcoded full URL database strings that include the username and password.

> 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
>            Priority: Blocker
>
> 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)