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

Joel Bernstein commented on SOLR-6266:
--------------------------------------

Karol,

Thanks for confirming the couchbase behavior. Let's see if we can reach 
consensus on the SolrCloud design. Here is what I propose:

1) I agree that having a CAPIServer per-collection makes the most sense for the 
reasons that Andrzej laid out. 

2) Based on your findings, let's go with simplest plan of having CAPIServers 
listening on all replicas. This will also be the most robust scenario and allow 
Couchbase to replicate in multiple threads to multiple nodes simultaneously.

3) In CouchbaseBehaviour.getNodesServingPool()  lets auto-discover the running 
CAPIServers from the existing Zookeeper state information. To keep things 
simple we could return all active replicas in the collection. Or we could ping 
each active node on the CAPIServer port to make sure the CAPIServer is running.

Let's also not keep any extra book-keeping in Zookeeper unless we absolutely 
have to for this ticket.

Joel


.

> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to