[
https://issues.apache.org/jira/browse/COUCHDB-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042256#comment-16042256
]
Joan Touzet commented on COUCHDB-3172:
--------------------------------------
There are plans to improve the integration of clouseau/dreyfus (and the Geo
addon, hastings/easton) to make them integrate without recompilation, but
probably not until 3.0.
I'm not closing this issue because you're right, it's still broken. Clustering
makes things more complex, since you need the service running on every node in
a cluster. I'm not sure how easily this can be done right now.
An easier approach might be to configure a new backend in the front-end load
balancer (such as haproxy, which is very commonly used in CouchDB cluster
deployments). This can do pattern-matching on the request URL and forward the
request to the appropriate backend, regardless of IP address or port.
> httpd_global_handlers proxy on main cluster interface
> -----------------------------------------------------
>
> Key: COUCHDB-3172
> URL: https://issues.apache.org/jira/browse/COUCHDB-3172
> Project: CouchDB
> Issue Type: Bug
> Reporter: Wiktor Obrębski
>
> couch_httpd_proxy looks like no working in main cluster 5984 interface in
> CouchDB 2.0.
> {code:title=config}
> [httpd_global_handlers]
> _fti = {couch_httpd_proxy, handle_proxy_req, <<"http://127.0.0.1:5985";>>}
> {code}
> it work only when I use direct node port (5986).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
