[
https://issues.apache.org/jira/browse/SOLR-17065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783241#comment-17783241
]
Kevin Risden commented on SOLR-17065:
-------------------------------------
So I'm not sure where to put this comment, but I am not sure this is a good
idea to bring into Solr main. I'd prefer we actually move some of the existing
modules out of Solr main. Each module brings in relatively heavy dependencies
that we need to keep upgrading and making sure they are all compatible.
Is there a reason this can't stay outside of main? There are multiple companies
using it without it being in the Solr main repo. Could it instead go to a
solr-modules or solr-plugins repo if the name "solr-sandbox" is not suitable?
> Migrate Sandbox CrossDC functionality into Solr
> -----------------------------------------------
>
> Key: SOLR-17065
> URL: https://issues.apache.org/jira/browse/SOLR-17065
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: CrossDC, module - crossDC
> Reporter: Houston Putman
> Assignee: Houston Putman
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> As a part of [SIP-13: Cross Data Center
> Replication|https://cwiki.apache.org/confluence/display/SOLR/SIP-13%3A+Cross+Data+Center+Replication],
> the [solr-sandbox|https://github.com/apache/solr-sandbox] repository was
> created and a new Cross DC implementation has been developed.
> This CrossDC implementation relies on Kafka (for now, maybe other queues in
> the future), and has two parts.
> * A producer, which is a Solr plugin (An updateRequestProcessor), that sends
> documents to kafka after successfully indexing them.
> * A consumer, which is a standalone application, that reads documents for
> kafka and sends them to the mirrored SolrClouds.
> This has been in development for a year now and is used at multiple companies
> (even in production).
> We believe that the project has reached a level of maturity that it can be
> "graduated" from the sandbox module and be included in future Solr releases.
>
> As a part of the move I propose the following:
> * The Producer will be branded as the "cross-dc" Solr module, and be
> available just as any other module is.
> * The Consumer will be branded as the "cross-dc-manager" and be packaged
> just as the prometheus-exporter is, a standalone application that comes with
> Solr and uses many of the same Jars. The reason for the name change is that
> we might expand the role of this application to something beyond just
> "consuming" from the Kafka queue. In that case its much easier to rename it
> now than later.
>
> We will let this bake in the main branch for a while before backporting to
> 9.x.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
