You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Gus Heck (Jira)" <ji...@apache.org> on 2020/07/01 17:47:00 UTC

[jira] [Commented] (SOLR-14022) Deprecate CDCR from Solr in 8.x

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

Gus Heck commented on SOLR-14022:
---------------------------------

Do we want to think about whether it's a good idea to have yet another set of technologies/servers to deploy to make solr work (fully)? Pulsar uses in Bookeeper and it looks like pulsar gets deployed as its own cluster. So this would lead to a minimum of 4 Solrs, 3 zookeepers and 3 pulsars for HA across regions. I've met clients who had trouble with the idea of separate zookeeper servers...

Another thing I'd like to say is a weakness of the existing CDCR is the use of collection names in config, which made it incompatible with routed aliases (where collections are added dynamically). A solution relying on external tools seems even less likely to be able to account for that. 

> Deprecate CDCR from Solr in 8.x
> -------------------------------
>
>                 Key: SOLR-14022
>                 URL: https://issues.apache.org/jira/browse/SOLR-14022
>             Project: Solr
>          Issue Type: Improvement
>          Components: CDCR
>            Reporter: Joel Bernstein
>            Assignee: Ishan Chattopadhyaya
>            Priority: Blocker
>             Fix For: 8.6
>
>
> This ticket will deprecate CDCR in Solr 8x.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org