You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by "Nick Vatamaniuc (JIRA)" <ji...@apache.org> on 2016/08/03 02:28:20 UTC

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

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

Nick Vatamaniuc commented on COUCHDB-2980:
------------------------------------------

[~chrisfosterelli] Interesting points.

Thinking more about this, it seems it is hard to for a node in a cluster to know the host of the cluster in general. Say a cluster is behind a proxy for fault tollerance, after the document is added to a replicator db, can't see how it would know what the external cluster host would be say database {{a}} means "https://user:pass@mycluster.com/a" or "http://user:pass@user.somecluster.net/a" for example. In case of {

> 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)