[
https://issues.apache.org/jira/browse/SOLR-14022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16993103#comment-16993103
]
Erick Erickson commented on SOLR-14022:
---------------------------------------
My thought is we should either go all in for supporting cross-DC
synchronization or remove it. The current status is "well, it kinda works, but
'there be dragons out there'" that it's up to the user to deal with.
"All in" here is fungible. I can imagine several ways of doing that:
1> commit to making CDCR robust enough to "just work".
1a> use the present "tlog as queue", but make it a "fire and forget unless you
see alerts"
1b> use an entirely different implementation. User's don't particularly care
_how_ it would work, as long as it's a Solr-only solution.
2> Decide that "all in" means "here's how you do cross-DC replication. Install
XXX and set these configuration parameters" where XXX is something freely
available. Kafka? Dropbox (that's a joke)? File replication? Heck, we could
even fsync to the remote site the _tlogs_ and consume them there (no, that's
not serious either, when brainstorming there are no bad ideas. Well, yes there
are, we just don't call them out yet).
My point is that CDCR serves a real need that users have. That said, we
shouldn't be hobbled by CDCR's current approach. Users care about having two
DCs stay in sync. Whether it's CDCR or "something else" is largely irrelevant,
can we address the root issue creatively?
> Remove CDCR from Solr
> ---------------------
>
> Key: SOLR-14022
> URL: https://issues.apache.org/jira/browse/SOLR-14022
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: CDCR
> Reporter: Joel Bernstein
> Priority: Major
>
> This ticket will remove CDCR from Solr
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
