lucene-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ctarg...@apache.org
Subject lucene-solr:branch_7_3: Ref Guide: fix bad link to another CDCR page
Date Mon, 26 Mar 2018 17:01:17 GMT
Repository: lucene-solr
Updated Branches:
  refs/heads/branch_7_3 a494138d6 -> f213f445e


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/f213f445
Tree: http://git-wip-us.apache.org/repos/asf/lucene-solr/tree/f213f445
Diff: http://git-wip-us.apache.org/repos/asf/lucene-solr/diff/f213f445

Branch: refs/heads/branch_7_3
Commit: f213f445e55591ab8bad67062ad1d3dc22d4c5ef
Parents: a494138
Author: Cassandra Targett <ctargett@apache.org>
Authored: Mon Mar 26 09:22:15 2018 -0500
Committer: Cassandra Targett <ctargett@apache.org>
Committed: Mon Mar 26 12:01:09 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/f213f445/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.
 


Mime
View raw message