[
https://issues.apache.org/jira/browse/SOLR-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14147850#comment-14147850
]
Karol Abramczyk edited comment on SOLR-6266 at 9/25/14 3:27 PM:
----------------------------------------------------------------
Joel,
I confirmed today, that Couchbase replicates each document to only one of the
running CAPIServers. My test configuration was Solr 1 and 2 running CAPIServers
1 and 2. Couchbase test bucket had 2 documents A and B. Only CAPIServer 1 was
configured for replication with Couchbase, but in
CouchbaseBehaviour.getNodesServingPool() method it was placing info about
itself and CAPIServer 2 as well. When replication finished, CAPIServer 1
indexed only document A, and CAPISErver 2 only document B. So you were right
about the Couchbase replication. But it also seems that only one CAPIServer
configured with Couchbase is sufficient as long as it knows about the other
CAPIServers in this cluster. We could register operating CAPIServers in
ZooKeeper, to have this info available for every node. I didn't check what
happens if more CAPIServers is configured with Couchabse XDCR.
was (Author: kabramcz):
Joel,
I confirmed today, that Couchbase replicates each document to only one of the
running CAPIServers. My test configuration was Solr 1 and 2 running CAPIServers
1 and 2. Couchbase test bucket had 2 documents A and B. Only CAPIServer 1 was
configured for replication with Couchbase, but in
CouchbaseBehaviour.getNodesServingPool() method it was placing info about
itself and CAPIServer 2 as well. So you were right about the Couchbase
replication. But it also seems that only one CAPIServer configured with
Couchbase is sufficient as long as it knows about the other CAPIServers in this
cluster. We could register operating CAPIServers in ZooKeeper, to have this
info available for every node. I didn't check what happens if more CAPIServers
is configured with Couchabse XDCR.
> Couchbase plug-in for Solr
> --------------------------
>
> Key: SOLR-6266
> URL: https://issues.apache.org/jira/browse/SOLR-6266
> Project: Solr
> Issue Type: New Feature
> Reporter: Varun
> Assignee: Joel Bernstein
> Attachments: solr-couchbase-plugin.tar.gz,
> solr-couchbase-plugin.tar.gz
>
>
> It would be great if users could connect Couchbase and Solr so that updates
> to Couchbase can automatically flow to Solr. Couchbase provides some very
> nice API's which allow applications to mimic the behavior of a Couchbase
> server so that it can receive updates via Couchbase's normal cross data
> center replication (XDCR).
> One possible design for this is to create a CouchbaseLoader that extends
> ContentStreamLoader. This new loader would embed the couchbase api's that
> listen for incoming updates from couchbase, then marshal the couchbase
> updates into the normal Solr update process.
> Instead of marshaling couchbase updates into the normal Solr update process,
> we could also embed a SolrJ client to relay the request through the http
> interfaces. This may be necessary if we have to handle mapping couchbase
> "buckets" to Solr collections on the Solr side.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
