You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by ct...@apache.org on 2018/03/26 17:00:29 UTC
lucene-solr:master: Ref Guide: fix bad link to another CDCR page
Repository: lucene-solr
Updated Branches:
refs/heads/master f4fb19fdc -> df9b88443
Ref Guide: fix bad link to another CDCR page
Project: http://git-wip-us.apache.org/repos/asf/lucene-solr/repo
Commit: http://git-wip-us.apache.org/repos/asf/lucene-solr/commit/df9b8844
Tree: http://git-wip-us.apache.org/repos/asf/lucene-solr/tree/df9b8844
Diff: http://git-wip-us.apache.org/repos/asf/lucene-solr/diff/df9b8844
Branch: refs/heads/master
Commit: df9b88443430a85c4bb00af63ff1da911584e6f5
Parents: f4fb19f
Author: Cassandra Targett <ct...@apache.org>
Authored: Mon Mar 26 09:22:15 2018 -0500
Committer: Cassandra Targett <ct...@apache.org>
Committed: Mon Mar 26 12:00:07 2018 -0500
----------------------------------------------------------------------
solr/solr-ref-guide/src/cdcr-architecture.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/df9b8844/solr/solr-ref-guide/src/cdcr-architecture.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/cdcr-architecture.adoc b/solr/solr-ref-guide/src/cdcr-architecture.adoc
index 40a5b91..bbd862f 100644
--- a/solr/solr-ref-guide/src/cdcr-architecture.adoc
+++ b/solr/solr-ref-guide/src/cdcr-architecture.adoc
@@ -88,7 +88,7 @@ In order to configure CDCR, the Source data center requires the host address of
CDCR supports incremental updates to either new or existing collections. CDCR may not be able to keep up with very high volume updates, especially if there are significant communications latencies due to a slow "pipe" between the data centers. Some scenarios:
-* There is an initial bulk load of a corpus followed by lower volume incremental updates. In this case, one can do the initial bulk load and then enable CDCR. See the section <<cdcr-config.adoc#initial-startup>> for more information.
+* There is an initial bulk load of a corpus followed by lower volume incremental updates. In this case, one can do the initial bulk load and then enable CDCR. See the section <<cdcr-config.adoc#initial-startup,Initial Startup>> for more information.
* The index is being built up from scratch, without a significant initial bulk load. CDCR can be set up on empty collections and keep them synchronized from the start.
* The index is always being updated at a volume too high for CDCR to keep up. This is especially possible in situations where the connection between the Source and Target data centers is poor. This scenario is unsuitable for CDCR in its current form.