[
https://issues.apache.org/jira/browse/COUCHDB-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15467500#comment-15467500
]
Nick Vatamaniuc commented on COUCHDB-2980:
------------------------------------------
Wonder if it is worth at least preventing creating local replications like the
original pr did? https://github.com/apache/couchdb-couch-replicator/pull/41
Otherwise behavior is surprising for someone with 1.x experience. And then
later even if we add a local clustered support (say in 2.1), it will all of the
sudden do something different.
In the meantime is using `http://localhost:5984/db` an alternative for users to
get the equivalent behavior? In other words would that cover Chris's case of
make replicator db work as expected if it is replicated to another cluster?
> 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)
