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 2017/05/09 19:22:32 UTC
svn commit: r1011953 [5/32] - in
/websites/production/lucene/content/solr/guide/test-10290: ./
fonts/mplus1mn/ images/a-quick-overview/ images/other-parsers/
Modified: websites/production/lucene/content/solr/guide/test-10290/cross-data-center-replication-cdcr-.html
==============================================================================
--- websites/production/lucene/content/solr/guide/test-10290/cross-data-center-replication-cdcr-.html (original)
+++ websites/production/lucene/content/solr/guide/test-10290/cross-data-center-replication-cdcr-.html Tue May 9 19:22:29 2017
@@ -1280,33 +1280,42 @@ $('#toc').on('click', 'a', function() {
<div id="preamble">
<div class="sectionbody">
<div class="paragraph">
-<p>The <a href="solrcloud.html#solrcloud">SolrCloud</a> architecture is not particularly well suited for situations where a single SolrCloud cluster consists of nodes in separated data clusters connected by an expensive pipe. The root problem is that SolrCloud is designed to support <a href="near-real-time-searching.html#near-real-time-searching">Near Real Time Searching</a> by immediately forwarding updates between nodes in the cluster on a per-shard basis. "CDCR" features exist to help mitigate the risk of an entire Data Center outage.</p>
+<p>Cross Data Center Replication (CDCR) allows you to create multiple SolrCloud data centers and keep them in sync in case they are needed at a future time.</p>
+</div>
+<div class="paragraph">
+<p>The <a href="solrcloud.html#solrcloud">SolrCloud</a> architecture is not particularly well suited for situations where a single SolrCloud cluster consists of nodes in separated data clusters connected by an expensive pipe. The root problem is that SolrCloud is designed to support <a href="near-real-time-searching.html#near-real-time-searching">Near Real Time Searching</a> by immediately forwarding updates between nodes in the cluster on a per-shard basis. "CDCR" features exist to help mitigate the risk of an entire data center outage.</p>
</div>
</div>
</div>
<div class="sect1">
-<h2 id="CrossDataCenterReplication_CDCR_-WhatisCDCR_">What is CDCR?</h2>
+<h2 id="what-is-cdcr">What is CDCR?</h2>
<div class="sectionbody">
<div class="paragraph">
-<p>The goal of the project is to replicate data to multiple Data Centers. The initial version of the solution will cover the active-passive scenario where data updates are replicated from a Source Data Center to one or more Target Data Centers. The Target Data Center(s) will not propagate updates to the Source Data Center and updates should <em>not</em> be sent to any of the Target Data Center(s). Data updates include adds, updates and deletes. Source and Target Data Centers can serve search queries when CDCR is operating. The Target Data Centers will have slightly stale views of the corpus due to propagation delays, but this is minimal (perhaps a few seconds).</p>
+<p>CDCR supports replicating data from one data center to multiple data centers. The initial version of the solution supports an active-passive scenario where data updates are replicated from a Source data center to one or more target data centers.</p>
+</div>
+<div class="paragraph">
+<p>The target data center(s) will not propagate updates such as adds, updates, or deletes to the source data center and updates should <em>not</em> be sent to any of the target data center(s).</p>
</div>
<div class="paragraph">
-<p>Data changes on the Source Data Center are replicated to the Target Data Center only after they are persisted to disk. The data changes can be replicated in real-time (with a small delay) or could be scheduled to be sent in intervals to the Target Data Center. This solution pre-supposes that the Source and Target data centers begin with the same documents indexed. Of course the indexes may be empty to start.</p>
+<p>Source and target data centers can serve search queries when CDCR is operating. The target data centers will have slightly stale views of the corpus due to propagation delays, but this is minimal (perhaps a few seconds).</p>
</div>
<div class="paragraph">
-<p>Each shard leader in the Source Data Center will be responsible for replicating its updates to the corresponding leader in the Target Data Center. When receiving updates from the Source Data Center, shard leaders in the Target Data Center will replicate the changes to their own replicas.</p>
+<p>Data changes on the source data center are replicated to the target data center only after they are persisted to disk. The data changes can be replicated in near real-time (with a small delay) or could be scheduled to be sent in intervals to the target data center. This solution pre-supposes that the source and target data centers begin with the same documents indexed. Of course the indexes may be empty to start.</p>
+</div>
+<div class="paragraph">
+<p>Each shard leader in the source data center will be responsible for replicating its updates to the corresponding leader in the target data center. When receiving updates from the source data center, shard leaders in the target data center will replicate the changes to their own replicas.</p>
</div>
<div class="paragraph">
<p>This replication model is designed to tolerate some degradation in connectivity, accommodate limited bandwidth, and support batch updates to optimize communication.</p>
</div>
<div class="paragraph">
-<p>Replication supports both a new empty index and pre-built indexes. In the scenario where the replication is set up on a pre-built index, CDCR will ensure consistency of the replication of the updates, but cannot ensure consistency on the full index. Therefore any index created before CDCR was set up will have to be replicated by other means (described in the section <a href="#CrossDataCenterReplication_CDCR_-InitialStartup">Initial Startup</a>) in order that Source and Target indexes be fully consistent.</p>
+<p>Replication supports both a new empty index and pre-built indexes. In the scenario where the replication is set up on a pre-built index, CDCR will ensure consistency of the replication of the updates, but cannot ensure consistency on the full index. Therefore any index created before CDCR was set up will have to be replicated by other means (described in the section <a href="#initial-startup">Initial Startup</a>) so source and target indexes are fully consistent.</p>
</div>
<div class="paragraph">
-<p>The active-passive nature of the initial implementation implies a "push" model from the Source collection to the Target collection. Therefore, the Source configuration must be able to "see" the ZooKeeper ensemble in the Target cluster. The ZooKeeper ensemble is provided configured in the Source’s <code>solrconfig.xml</code> file.</p>
+<p>The active-passive nature of the initial implementation implies a "push" model from the source collection to the target collection. Therefore, the source configuration must be able to "see" the ZooKeeper ensemble in the target cluster. The ZooKeeper ensemble is provided configured in the Source’s <code>solrconfig.xml</code> file.</p>
</div>
<div class="paragraph">
-<p>CDCR is configured to replicate from collections in the Source cluster to collections in the Target cluster on a collection-by-collection basis. Since CDCR is configured in <code>solrconfig.xml</code> (on both Source and Target clusters), the settings can be tailored for the needs of each collection.</p>
+<p>CDCR is configured to replicate from collections in the source cluster to collections in the target cluster on a collection-by-collection basis. Since CDCR is configured in <code>solrconfig.xml</code> (on both source and target clusters), the settings can be tailored for the needs of each collection.</p>
</div>
<div class="paragraph">
<p>CDCR can be configured to replicate from one collection to a second collection <em>within the same cluster</em>. That is a specialized scenario not covered in this document.</p>
@@ -1314,46 +1323,55 @@ $('#toc').on('click', 'a', function() {
</div>
</div>
<div class="sect1">
-<h2 id="CrossDataCenterReplication_CDCR_-Glossary">Glossary</h2>
+<h2 id="cdcr-glossary">CDCR Glossary</h2>
<div class="sectionbody">
<div class="paragraph">
<p>Terms used in this document include:</p>
</div>
-<div class="ulist">
-<ul>
-<li>
-<p><strong>Node</strong>: A JVM instance running Solr; a server.</p>
-</li>
-<li>
-<p><strong>Cluster</strong>: A set of Solr nodes managed as a single unit by a ZooKeeper ensemble, hosting one or more Collections.</p>
-</li>
-<li>
-<p><strong>Data Center:</strong> A group of networked servers hosting a Solr cluster. In this document, the terms <em>Cluster</em> and <em>Data Center</em> are interchangeable as we assume that each Solr cluster is hosted in a different group of networked servers.</p>
-</li>
-<li>
-<p><strong>Shard</strong>: A sub-index of a single logical collection. This may be spread across multiple nodes of the cluster. Each shard can have as many replicas as needed.</p>
-</li>
-<li>
-<p><strong>Leader</strong>: Each shard has one node identified as its leader. All the writes for documents belonging to a shard are routed through the leader.</p>
-</li>
-<li>
-<p><strong>Replica</strong>: A copy of a shard for use in failover or load balancing. Replicas comprising a shard can either be leaders or non-leaders.</p>
-</li>
-<li>
-<p><strong>Follower:</strong> A convenience term for a replica that is <em>not</em> the leader of a shard.</p>
-</li>
-<li>
-<p><strong>Collection</strong>: Multiple documents that make up one logical index. A cluster can have multiple collections.</p>
-</li>
-<li>
-<p><strong>Updates Log</strong>: An append-only log of write operations maintained by each node.</p>
-</li>
-</ul>
+<div class="dlist glossary">
+<dl>
+<dt>Node</dt>
+<dd>
+<p>A JVM instance running Solr; a server.</p>
+</dd>
+<dt>Cluster</dt>
+<dd>
+<p>A set of Solr nodes managed as a single unit by a ZooKeeper ensemble, hosting one or more Collections.</p>
+</dd>
+<dt>Data Center</dt>
+<dd>
+<p>A group of networked servers hosting a Solr cluster. In this document, the terms <em>Cluster</em> and <em>Data Center</em> are interchangeable as we assume that each Solr cluster is hosted in a different group of networked servers.</p>
+</dd>
+<dt>Shard</dt>
+<dd>
+<p>A sub-index of a single logical collection. This may be spread across multiple nodes of the cluster. Each shard can have as many replicas as needed.</p>
+</dd>
+<dt>Leader</dt>
+<dd>
+<p>Each shard has one node identified as its leader. All the writes for documents belonging to a shard are routed through the leader.</p>
+</dd>
+<dt>Replica</dt>
+<dd>
+<p>A copy of a shard for use in failover or load balancing. Replicas comprising a shard can either be leaders or non-leaders.</p>
+</dd>
+<dt>Follower</dt>
+<dd>
+<p>A convenience term for a replica that is <em>not</em> the leader of a shard.</p>
+</dd>
+<dt>Collection</dt>
+<dd>
+<p>Multiple documents that make up one logical index. A cluster can have multiple collections.</p>
+</dd>
+<dt>Updates Log</dt>
+<dd>
+<p>An append-only log of write operations maintained by each node.</p>
+</dd>
+</dl>
</div>
</div>
</div>
<div class="sect1">
-<h2 id="CrossDataCenterReplication_CDCR_-Architecture">Architecture</h2>
+<h2 id="cdcr-architecture">CDCR Architecture</h2>
<div class="sectionbody">
<div class="paragraph">
<p>Here is a picture of the data flow.</p>
@@ -1362,6 +1380,7 @@ $('#toc').on('click', 'a', function() {
<div class="content">
<img src="images/cross-data-center-replication-cdcr-/CDCR_arch.png" alt="image" width="700" height="525">
</div>
+<div class="title">Figure 1. CDCR Data Flow</div>
</div>
<div class="paragraph">
<p>Updates and deletes are first written to the Source cluster, then forwarded to the Target cluster. The data flow sequence is:</p>
@@ -1369,7 +1388,7 @@ $('#toc').on('click', 'a', function() {
<div class="olist arabic">
<ol class="arabic">
<li>
-<p>A shard leader receives a new data update that is processed by its Update Processor.</p>
+<p>A shard leader receives a new data update that is processed by its update processor chain.</p>
</li>
<li>
<p>The data update is first applied to the local index.</p>
@@ -1378,86 +1397,86 @@ $('#toc').on('click', 'a', function() {
<p>Upon successful application of the data update on the local index, the data update is added to the Updates Log queue.</p>
</li>
<li>
-<p>After the data update is persisted to disk, the data update is sent to the replicas within the Data Center.</p>
+<p>After the data update is persisted to disk, the data update is sent to the replicas within the data center.</p>
</li>
<li>
-<p>After Step 4 is successful CDCR reads the data update from the Updates Log and pushes it to the corresponding collection in the Target Data Center. This is necessary in order to ensure consistency between the Source and Target Data Centers.</p>
+<p>After Step 4 is successful, CDCR reads the data update from the Updates Log and pushes it to the corresponding collection in the target data center. This is necessary in order to ensure consistency between the Source and target data centers.</p>
</li>
<li>
-<p>The leader on the Target data center writes the data locally and forwards it to all its followers.</p>
+<p>The leader on the target data center writes the data locally and forwards it to all its followers.</p>
</li>
</ol>
</div>
<div class="paragraph">
-<p>Steps 1, 2, 3 and 4 are performed synchronously by SolrCloud; Step 5 is performed asynchronously by a background thread. Given that CDCR replication is performed asynchronously, it becomes possible to push batch updates in order to minimize network communication overhead. Also, if CDCR is unable to push the update at a given time — for example, due to a degradation in connectivity — it can retry later without any impact on the Source Data Center.</p>
+<p>Steps 1, 2, 3 and 4 are performed synchronously by SolrCloud; Step 5 is performed asynchronously by a background thread. Given that CDCR replication is performed asynchronously, it becomes possible to push batch updates in order to minimize network communication overhead. Also, if CDCR is unable to push the update at a given time, for example, due to a degradation in connectivity, it can retry later without any impact on the source data center.</p>
</div>
<div class="paragraph">
-<p>One implication of the architecture is that the leaders in the Source cluster must be able to "see" the leaders in the Target cluster. Since leaders may change, this effectively means that all nodes in the Source cluster must be able to "see" all Solr nodes in the Target cluster so firewalls, ACL rules, etc. must be configured with care.</p>
+<p>One implication of the architecture is that the leaders in the source cluster must be able to "see" the leaders in the target cluster. Since leaders may change, this effectively means that all nodes in the source cluster must be able to "see" all Solr nodes in the target cluster so firewalls, ACL rules, etc. must be configured with care.</p>
</div>
<div class="paragraph">
-<p>The current design works most robustly if both the Source and Target clusters have the same number of shards. There is no requirement that the shards in the Source and Target collection have the same number of replicas.</p>
+<p>The current design works most robustly if both the Source and target clusters have the same number of shards. There is no requirement that the shards in the Source and target collection have the same number of replicas.</p>
</div>
<div class="paragraph">
-<p>Having different numbers of shards on the Source and Target cluster is possible, but is also an "expert" configuration as that option imposes certain constraints and is not recommended. Most of the scenarios where having differing numbers of shards are contemplated are better accomplished by hosting multiple shards on each Target Solr instance.</p>
+<p>Having different numbers of shards on the Source and target cluster is possible, but is also an "expert" configuration as that option imposes certain constraints and is not recommended. Most of the scenarios where having differing numbers of shards are contemplated are better accomplished by hosting multiple shards on each target Solr instance.</p>
</div>
</div>
</div>
<div class="sect1">
-<h2 id="CrossDataCenterReplication_CDCR_-MajorComponents">Major Components</h2>
+<h2 id="major-components-of-cdcr">Major Components of CDCR</h2>
<div class="sectionbody">
<div class="paragraph">
<p>There are a number of key features and components in CDCRâs architecture:</p>
</div>
<div class="sect2">
-<h3 id="CrossDataCenterReplication_CDCR_-CDCRConfiguration">CDCR Configuration</h3>
+<h3 id="cdcr-configuration">CDCR Configuration</h3>
<div class="paragraph">
-<p>In order to configure CDCR, the Source Data Center requires the host address of the ZooKeeper cluster associated with the Target Data Center. The ZooKeeper host address is the only information needed by CDCR to instantiate the communication with the Target Solr cluster. The CDCR configuration file on the Source cluster will therefore contain a list of ZooKeeper hosts. The CDCR configuration file might also contain secondary/optional configuration, such as the number of CDC Replicator threads, batch updates related settings, etc.</p>
+<p>In order to configure CDCR, the Source data center requires the host address of the ZooKeeper cluster associated with the target data center. The ZooKeeper host address is the only information needed by CDCR to instantiate the communication with the target Solr cluster. The CDCR configuration file on the source cluster will therefore contain a list of ZooKeeper hosts. The CDCR configuration file might also contain secondary/optional configuration, such as the number of CDC Replicator threads, batch updates related settings, etc.</p>
</div>
</div>
<div class="sect2">
-<h3 id="CrossDataCenterReplication_CDCR_-CDCRInitialization">CDCR Initialization</h3>
+<h3 id="cdcr-initialization">CDCR Initialization</h3>
<div class="paragraph">
<p>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:</p>
</div>
<div class="ulist">
<ul>
<li>
-<p>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 <a href="#CrossDataCenterReplication_CDCR_-InitialStartup">Initial Startup</a> for more information.</p>
+<p>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 <a href="#initial-startup">Initial Startup</a> for more information.</p>
</li>
<li>
<p>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.</p>
</li>
<li>
-<p>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.</p>
+<p>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.</p>
</li>
</ul>
</div>
</div>
<div class="sect2">
-<h3 id="CrossDataCenterReplication_CDCR_-Inter-DataCenterCommunication">Inter-Data Center Communication</h3>
+<h3 id="inter-data-center-communication">Inter-Data Center Communication</h3>
<div class="paragraph">
-<p>Communication between Data Centers will be achieved through HTTP and the Solr REST API using the SolrJ client. The SolrJ client will be instantiated with the ZooKeeper host of the Target Data Center. SolrJ will manage the shard leader discovery process.</p>
+<p>Communication between data centers will be achieved through HTTP and the Solr REST API using the SolrJ client. The SolrJ client will be instantiated with the ZooKeeper host of the target data center. SolrJ will manage the shard leader discovery process.</p>
</div>
</div>
<div class="sect2">
-<h3 id="CrossDataCenterReplication_CDCR_-UpdatesTracking_Pushing">Updates Tracking & Pushing</h3>
+<h3 id="updates-tracking-pushing">Updates Tracking & Pushing</h3>
<div class="paragraph">
-<p>CDCR replicates data updates from the Source to the Target Data Center by leveraging the Updates Log.</p>
+<p>CDCR replicates data updates from the source to the target data center by leveraging the Updates Log.</p>
</div>
<div class="paragraph">
-<p>A background thread regularly checks the Updates Log for new entries, and then forwards them to the Target Data Center. The thread therefore needs to keep a checkpoint in the form of a pointer to the last update successfully processed in the Updates Log. Upon acknowledgement from the Target Data Center that updates have been successfully processed, the Updates Log pointer is updated to reflect the current checkpoint.</p>
+<p>A background thread regularly checks the Updates Log for new entries, and then forwards them to the target data center. The thread therefore needs to keep a checkpoint in the form of a pointer to the last update successfully processed in the Updates Log. Upon acknowledgement from the target data center that updates have been successfully processed, the Updates Log pointer is updated to reflect the current checkpoint.</p>
</div>
<div class="paragraph">
<p>This pointer must be synchronized across all the replicas. In the case where the leader goes down and a new leader is elected, the new leader will be able to resume replication from the last update by using this synchronized pointer. The strategy to synchronize such a pointer across replicas will be explained next.</p>
</div>
<div class="paragraph">
-<p>If for some reason, the Target Data Center is offline or fails to process the updates, the thread will periodically try to contact the Target Data Center and push the updates.</p>
+<p>If for some reason, the target data center is offline or fails to process the updates, the thread will periodically try to contact the target data center and push the updates.</p>
</div>
</div>
<div class="sect2">
-<h3 id="CrossDataCenterReplication_CDCR_-SynchronizationofUpdateCheckpoints">Synchronization of Update Checkpoints</h3>
+<h3 id="synchronization-of-update-checkpoints">Synchronization of Update Checkpoints</h3>
<div class="paragraph">
-<p>A reliable synchronization of the update checkpoints between the shard leader and shard replicas is critical to avoid introducing inconsistency between the Source and Target Data Centers. Another important requirement is that the synchronization must be performed with minimal network traffic to maximize scalability.</p>
+<p>A reliable synchronization of the update checkpoints between the shard leader and shard replicas is critical to avoid introducing inconsistency between the Source and target data centers. Another important requirement is that the synchronization must be performed with minimal network traffic to maximize scalability.</p>
</div>
<div class="paragraph">
<p>In order to achieve this, the strategy is to:</p>
@@ -1468,18 +1487,18 @@ $('#toc').on('click', 'a', function() {
<p>Uniquely identify each update operation. This unique identifier will serve as pointer.</p>
</li>
<li>
-<p>Rely on two storages: an ephemeral storage on the Source shard leader, and a persistent storage on the Target cluster.</p>
+<p>Rely on two storages: an ephemeral storage on the Source shard leader, and a persistent storage on the target cluster.</p>
</li>
</ul>
</div>
<div class="paragraph">
-<p>The shard leader in the Source cluster will be in charge of generating a unique identifier for each update operation, and will keep a copy of the identifier of the last processed updates in memory. The identifier will be sent to the Target cluster as part of the update request. On the Target Data Center side, the shard leader will receive the update request, store it along with the unique identifier in the Updates Log, and replicate it to the other shards.</p>
+<p>The shard leader in the source cluster will be in charge of generating a unique identifier for each update operation, and will keep a copy of the identifier of the last processed updates in memory. The identifier will be sent to the target cluster as part of the update request. On the target data center side, the shard leader will receive the update request, store it along with the unique identifier in the Updates Log, and replicate it to the other shards.</p>
</div>
<div class="paragraph">
-<p>SolrCloud is already providing a unique identifier for each update operation, i.e., a âversionâ number. This version number is generated using a time-based lmport clock which is incremented for each update operation sent. This provides an âhappened-beforeâ ordering of the update operations that will be leveraged in (1) the initialization of the update checkpoint on the Source cluster, and in (2) the maintenance strategy of the Updates Log.</p>
+<p>SolrCloud already provides a unique identifier for each update operation, i.e., a âversionâ number. This version number is generated using a time-based lmport clock which is incremented for each update operation sent. This provides an âhappened-beforeâ ordering of the update operations that will be leveraged in (1) the initialization of the update checkpoint on the source cluster, and in (2) the maintenance strategy of the Updates Log.</p>
</div>
<div class="paragraph">
-<p>The persistent storage on the Target cluster is used only during the election of a new shard leader on the Source cluster. If a shard leader goes down on the Source cluster and a new leader is elected, the new leader will contact the Target cluster to retrieve the last update checkpoint and instantiate its ephemeral pointer. On such a request, the Target cluster will retrieve the latest identifier received across all the shards, and send it back to the Source cluster. To retrieve the latest identifier, every shard leader will look up the identifier of the first entry in its Update Logs and send it back to a coordinator. The coordinator will have to select the highest among them.</p>
+<p>The persistent storage on the target cluster is used only during the election of a new shard leader on the Source cluster. If a shard leader goes down on the source cluster and a new leader is elected, the new leader will contact the target cluster to retrieve the last update checkpoint and instantiate its ephemeral pointer. On such a request, the target cluster will retrieve the latest identifier received across all the shards, and send it back to the source cluster. To retrieve the latest identifier, every shard leader will look up the identifier of the first entry in its Update Logs and send it back to a coordinator. The coordinator will have to select the highest among them.</p>
</div>
<div class="paragraph">
<p>This strategy does not require any additional network traffic and ensures reliable pointer synchronization. Consistency is principally achieved by leveraging SolrCloud. The update workflow of SolrCloud ensures that every update is applied to the leader but also to any of the replicas. If the leader goes down, a new leader is elected. During the leader election, a synchronization is performed between the new leader and the other replicas. As a result, this ensures that the new leader has a consistent Update Logs with the previous leader. Having a consistent Updates Log means that:</p>
@@ -1487,21 +1506,21 @@ $('#toc').on('click', 'a', function() {
<div class="ulist">
<ul>
<li>
-<p>On the Source cluster, the update checkpoint can be reused by the new leader.</p>
+<p>On the source cluster, the update checkpoint can be reused by the new leader.</p>
</li>
<li>
-<p>On the Target cluster, the update checkpoint will be consistent between the previous and new leader. This ensures the correctness of the update checkpoint sent by a newly elected leader from the Target cluster.</p>
+<p>On the target cluster, the update checkpoint will be consistent between the previous and new leader. This ensures the correctness of the update checkpoint sent by a newly elected leader from the target cluster.</p>
</li>
</ul>
</div>
</div>
<div class="sect2">
-<h3 id="CrossDataCenterReplication_CDCR_-MaintenanceofUpdatesLog">Maintenance of Updates Log</h3>
+<h3 id="maintenance-of-updates-log">Maintenance of Updates Log</h3>
<div class="paragraph">
-<p>The CDCR replication logic requires modification to the maintenance logic of the Updates Log on the Source Data Center. Initially, the Updates Log acts as a fixed size queue, limited to 100 update entries. In the CDCR scenario, the Update Logs must act as a queue of variable size as they need to keep track of all the updates up through the last processed update by the Target Data Center. Entries in the Update Logs are removed only when all pointers (one pointer per Target Data Center) are after them.</p>
+<p>The CDCR replication logic requires modification to the maintenance logic of the Updates Log on the source data center. Initially, the Updates Log acts as a fixed size queue, limited to 100 update entries. In the CDCR scenario, the Update Logs must act as a queue of variable size as they need to keep track of all the updates up through the last processed update by the target data center. Entries in the Update Logs are removed only when all pointers (one pointer per target data center) are after them.</p>
</div>
<div class="paragraph">
-<p>If the communication with one of the Target Data Center is slow, the Updates Log on the Source Data Center can grow to a substantial size. In such a scenario, it is necessary for the Updates Log to be able to efficiently find a given update operation given its identifier. Given that its identifier is an incremental number, it is possible to implement an efficient search strategy. Each transaction log file contains as part of its filename the version number of the first element. This is used to quickly traverse all the transaction log files and find the transaction log file containing one specific version number.</p>
+<p>If the communication with one of the target data center is slow, the Updates Log on the source data center can grow to a substantial size. In such a scenario, it is necessary for the Updates Log to be able to efficiently find a given update operation given its identifier. Given that its identifier is an incremental number, it is possible to implement an efficient search strategy. Each transaction log file contains as part of its filename the version number of the first element. This is used to quickly traverse all the transaction log files and find the transaction log file containing one specific version number.</p>
</div>
</div>
<div class="sect2">
@@ -1512,7 +1531,7 @@ $('#toc').on('click', 'a', function() {
<div class="ulist">
<ul>
<li>
-<p>Monitoring of the outgoing and incoming replications, with information such as the Source and Target nodes, their status, etc.</p>
+<p>Monitoring of the outgoing and incoming replications, with information such as the Source and target nodes, their status, etc.</p>
</li>
<li>
<p>Statistics about the replication, with information such as operations (add/delete) per second, number of documents in the queue, etc.</p>
@@ -1524,9 +1543,9 @@ $('#toc').on('click', 'a', function() {
</div>
</div>
<div class="sect2">
-<h3 id="CrossDataCenterReplication_CDCR_-CDCReplicator">CDC Replicator</h3>
+<h3 id="cdc-replicator">CDC Replicator</h3>
<div class="paragraph">
-<p>The CDC Replicator is a background thread that is responsible for replicating updates from a Source Data Center to one or more Target Data Centers. It will also be responsible in providing monitoring information on a per-shard basis. As there can be a large number of collections and shards in a cluster, we will use a fixed-size pool of CDC Replicator threads that will be shared across shards.</p>
+<p>The CDC Replicator is a background thread that is responsible for replicating updates from a Source data center to one or more target data centers. It is responsible in providing monitoring information on a per-shard basis. As there can be a large number of collections and shards in a cluster, we will use a fixed-size pool of CDC Replicator threads that will be shared across shards.</p>
</div>
</div>
<div class="sect2">
@@ -1537,13 +1556,13 @@ $('#toc').on('click', 'a', function() {
<div class="ulist">
<ul>
<li>
-<p>CDCR is unlikely to be satisfactory for bulk-load situations where the update rate is high, especially if the bandwidth between the Source and Target clusters is restricted. In this scenario, the initial bulk load should be performed, the Source and Target data centers synchronized and CDCR be utilized for incremental updates.</p>
+<p>CDCR is unlikely to be satisfactory for bulk-load situations where the update rate is high, especially if the bandwidth between the Source and target clusters is restricted. In this scenario, the initial bulk load should be performed, the Source and target data centers synchronized and CDCR be utilized for incremental updates.</p>
</li>
<li>
-<p>CDCR is currently only active-passive; data is pushed from the Source cluster to the Target cluster. There is active work being done in this area in the 6x code line to remove this limitation.</p>
+<p>CDCR is currently only active-passive; data is pushed from the Source cluster to the target cluster. There is active work being done in this area in the 6x code line to remove this limitation.</p>
</li>
<li>
-<p>CDCR works most robustly with the same number of shards in the Source and Target collection. The shards in the two collections may have different numbers of replicas.</p>
+<p>CDCR works most robustly with the same number of shards in the Source and target collection. The shards in the two collections may have different numbers of replicas.</p>
</li>
</ul>
</div>
@@ -1554,15 +1573,12 @@ $('#toc').on('click', 'a', function() {
<h2 id="CrossDataCenterReplication_CDCR_-Configuration">Configuration</h2>
<div class="sectionbody">
<div class="paragraph">
-<p>The Source and Target configurations differ in the case of the data centers being in separate clusters. "Cluster" here means separate ZooKeeper ensembles controlling disjoint Solr instances. Whether these data centers are physically separated or not is immaterial for this discussion.</p>
-</div>
-<div id="CrossDataCenterReplication_CDCR_-Configuration" class="paragraph">
-<p>===</p>
+<p>The source and target configurations differ in the case of the data centers being in separate clusters. "Cluster" here means separate ZooKeeper ensembles controlling disjoint Solr instances. Whether these data centers are physically separated or not is immaterial for this discussion.</p>
</div>
<div class="sect2">
<h3 id="CrossDataCenterReplication_CDCR_-SourceConfiguration">Source Configuration</h3>
<div class="paragraph">
-<p>Here is a sample of a Source configuration file, a section in <code>solrconfig.xml</code>. The presence of the <replica> section causes CDCR to use this cluster as the Source and should not be present in the Target collections in the cluster-to-cluster case. Details about each setting are after the two examples:</p>
+<p>Here is a sample of a source configuration file, a section in <code>solrconfig.xml</code>. The presence of the <replica> section causes CDCR to use this cluster as the Source and should not be present in the target collections in the cluster-to-cluster case. Details about each setting are after the two examples:</p>
</div>
<div class="listingblock">
<div class="content">
@@ -1598,10 +1614,10 @@ $('#toc').on('click', 'a', function() {
<div class="sect2">
<h3 id="CrossDataCenterReplication_CDCR_-TargetConfiguration">Target Configuration</h3>
<div class="paragraph">
-<p>Here is a typical Target configuration.</p>
+<p>Here is a typical target configuration.</p>
</div>
<div class="paragraph">
-<p>Target instance must configure an update processor chain that is specific to CDCR. The update processor chain must include the <strong>CdcrUpdateProcessorFactory</strong>. The task of this processor is to ensure that the version numbers attached to update requests coming from a CDCR Source SolrCloud are reused and not overwritten by the Target. A properly configured Target configuration looks similar to this.</p>
+<p>Target instance must configure an update processor chain that is specific to CDCR. The update processor chain must include the <strong>CdcrUpdateProcessorFactory</strong>. The task of this processor is to ensure that the version numbers attached to update requests coming from a CDCR source SolrCloud are reused and not overwritten by the target. A properly configured Target configuration looks similar to this.</p>
</div>
<div class="listingblock">
<div class="content">
@@ -1634,21 +1650,21 @@ $('#toc').on('click', 'a', function() {
</div>
</div>
<div class="sect2">
-<h3 id="CrossDataCenterReplication_CDCR_-ConfigurationDetails">Configuration Details</h3>
+<h3 id="configuration-details">Configuration Details</h3>
<div class="paragraph">
<p>The configuration details, defaults and options are as follows:</p>
</div>
<div class="sect3">
-<h4 id="CrossDataCenterReplication_CDCR_-TheReplicaElement">The Replica Element</h4>
+<h4 id="the-replica-element">The Replica Element</h4>
<div class="paragraph">
<p>CDCR can be configured to forward update requests to one or more replicas. A replica is defined with a âreplicaâ list as follows:</p>
</div>
<table class="tableblock frame-all grid-all spread">
<colgroup>
-<col style="width: 25%;">
-<col style="width: 25%;">
-<col style="width: 25%;">
-<col style="width: 25%;">
+<col style="width: 20%;">
+<col style="width: 10%;">
+<col style="width: 15%;">
+<col style="width: 55%;">
</colgroup>
<thead>
<tr>
@@ -1663,7 +1679,7 @@ $('#toc').on('click', 'a', function() {
<td class="tableblock halign-left valign-top"><p class="tableblock">zkHost</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Yes</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">none</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">The host address for ZooKeeper of the Target SolrCloud. Usually this is a comma-separated list of addresses to each node in the Target ZooKeeper ensemble.</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The host address for ZooKeeper of the target SolrCloud. Usually this is a comma-separated list of addresses to each node in the target ZooKeeper ensemble.</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Source</p></td>
@@ -1675,22 +1691,25 @@ $('#toc').on('click', 'a', function() {
<td class="tableblock halign-left valign-top"><p class="tableblock">Target</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Yes</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">none</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">The name of the collection on the Target SolrCloud to which updates will be forwarded.</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The name of the collection on the target SolrCloud to which updates will be forwarded.</p></td>
</tr>
</tbody>
</table>
</div>
<div class="sect3">
-<h4 id="CrossDataCenterReplication_CDCR_-TheReplicatorElement">The Replicator Element</h4>
+<h4 id="the-replicator-element">The Replicator Element</h4>
<div class="paragraph">
-<p>The CDC Replicator is the component in charge of forwarding updates to the replicas. The replicator will monitor the update logs of the Source collection and will forward any new updates to the Target collection. The replicator uses a fixed thread pool to forward updates to multiple replicas in parallel. If more than one replica is configured, one thread will forward a batch of updates from one replica at a time in a round-robin fashion. The replicator can be configured with a âreplicatorâ list as follows:</p>
+<p>The CDC Replicator is the component in charge of forwarding updates to the replicas. The replicator will monitor the update logs of the Source collection and will forward any new updates to the target collection.</p>
+</div>
+<div class="paragraph">
+<p>The replicator uses a fixed thread pool to forward updates to multiple replicas in parallel. If more than one replica is configured, one thread will forward a batch of updates from one replica at a time in a round-robin fashion. The replicator can be configured with a âreplicatorâ list as follows:</p>
</div>
<table class="tableblock frame-all grid-all spread">
<colgroup>
-<col style="width: 25%;">
-<col style="width: 25%;">
-<col style="width: 25%;">
-<col style="width: 25%;">
+<col style="width: 20%;">
+<col style="width: 10%;">
+<col style="width: 15%;">
+<col style="width: 55%;">
</colgroup>
<thead>
<tr>
@@ -1723,16 +1742,16 @@ $('#toc').on('click', 'a', function() {
</table>
</div>
<div class="sect3">
-<h4 id="CrossDataCenterReplication_CDCR_-TheupdateLogSynchronizerElement">The updateLogSynchronizer Element</h4>
+<h4 id="the-updatelogsynchronizer-element">The updateLogSynchronizer Element</h4>
<div class="paragraph">
<p>Expert: Non-leader nodes need to synchronize their update logs with their leader node from time to time in order to clean deprecated transaction log files. By default, such a synchronization process is performed every minute. The schedule of the synchronization can be modified with a âupdateLogSynchronizerâ list as follows:</p>
</div>
<table class="tableblock frame-all grid-all spread">
<colgroup>
-<col style="width: 25%;">
-<col style="width: 25%;">
-<col style="width: 25%;">
-<col style="width: 25%;">
+<col style="width: 20%;">
+<col style="width: 10%;">
+<col style="width: 15%;">
+<col style="width: 55%;">
</colgroup>
<thead>
<tr>
@@ -1753,16 +1772,16 @@ $('#toc').on('click', 'a', function() {
</table>
</div>
<div class="sect3">
-<h4 id="CrossDataCenterReplication_CDCR_-TheBufferElement">The Buffer Element</h4>
+<h4 id="the-buffer-element">The Buffer Element</h4>
<div class="paragraph">
-<p>CDCR is configured by default to buffer any new incoming updates. When buffering updates, the updates log will store all the updates indefinitely. Replicas do not need to buffer updates, and it is recommended to disable buffer on the Target SolrCloud. The buffer can be disabled at startup with a âbufferâ list and the parameter âdefaultStateâ as follows:</p>
+<p>CDCR is configured by default to buffer any new incoming updates. When buffering updates, the updates log will store all the updates indefinitely. Replicas do not need to buffer updates, and it is recommended to disable buffer on the target SolrCloud. The buffer can be disabled at startup with a âbufferâ list and the parameter âdefaultStateâ as follows:</p>
</div>
<table class="tableblock frame-all grid-all spread">
<colgroup>
-<col style="width: 25%;">
-<col style="width: 25%;">
-<col style="width: 25%;">
-<col style="width: 25%;">
+<col style="width: 20%;">
+<col style="width: 10%;">
+<col style="width: 15%;">
+<col style="width: 55%;">
</colgroup>
<thead>
<tr>
@@ -1786,57 +1805,85 @@ $('#toc').on('click', 'a', function() {
</div>
</div>
<div class="sect1">
-<h2 id="CrossDataCenterReplication_CDCR_-CDCRAPI">CDCR API</h2>
+<h2 id="cdcr-api">CDCR API</h2>
<div class="sectionbody">
<div class="paragraph">
-<p>The CDCR API is used to control and monitor the replication process. Control actions are performed at a collection level, i.e., by using the following base URL for API calls: <code><a href="http://<hostname>:<port>/solr/<collection>" class="bare">http://<hostname>:<port>/solr/<collection></a>;</code>. Monitor actions are performed at a core level, i.e., by using the following base URL for API calls: <code><a href="http://<hostname>:<port>/solr/<collection>" class="bare">http://<hostname>:<port>/solr/<collection></a>;</code>.</p>
+<p>The CDCR API is used to control and monitor the replication process. Control actions are performed at a collection level, i.e., by using the following base URL for API calls: <code>http://localhost:8983/solr/<collection></code>.</p>
+</div>
+<div class="paragraph">
+<p>Monitor actions are performed at a core level, i.e., by using the following base URL for API calls: <code>http://localhost:8983/solr/<collection></code>.</p>
</div>
<div class="paragraph">
<p>Currently, none of the CDCR API calls have parameters.</p>
</div>
<div class="sect2">
-<h3 id="CrossDataCenterReplication_CDCR_-APIEntryPoints_Control_">API Entry Points (Control)</h3>
-<div class="paragraph">
-<p><code>collection/cdcr?action=STATUS</code>: <a href="#CrossDataCenterReplication_CDCR_-STATUS">Returns the current state</a> of CDCR. <code>collection/cdcr?action=START</code>: <a href="#CrossDataCenterReplication_CDCR_-START">Starts CDCR</a> replication <code>collection/cdcr?action=STOP</code>: <a href="#CrossDataCenterReplication_CDCR_-STOP">Stops CDCR</a> replication. <code>collection/cdcr?action=ENABLEBUFFER</code>: <a href="#CrossDataCenterReplication_CDCR_-ENABLEBUFFER">Enables the buffering</a> of updates. <code>collection/cdcr?action=DISABLEBUFFER</code>: <a href="#CrossDataCenterReplication_CDCR_-DISABLEBUFFER">Disables the buffering</a> of updates.</p>
+<h3 id="api-entry-points-control">API Entry Points (Control)</h3>
+<div class="ulist">
+<ul>
+<li>
+<p><code><collection>/cdcr?action=STATUS</code>: <a href="#CrossDataCenterReplication_CDCR_-STATUS">Returns the current state</a> of CDCR.</p>
+</li>
+<li>
+<p><code><collection>/cdcr?action=START</code>: <a href="#CrossDataCenterReplication_CDCR_-START">Starts CDCR</a> replication</p>
+</li>
+<li>
+<p><code><collection>/cdcr?action=STOP</code>: <a href="#CrossDataCenterReplication_CDCR_-STOP">Stops CDCR</a> replication.</p>
+</li>
+<li>
+<p><code><collection>/cdcr?action=ENABLEBUFFER</code>: <a href="#CrossDataCenterReplication_CDCR_-ENABLEBUFFER">Enables the buffering</a> of updates.</p>
+</li>
+<li>
+<p><code><collection>/cdcr?action=DISABLEBUFFER</code>: <a href="#CrossDataCenterReplication_CDCR_-DISABLEBUFFER">Disables the buffering</a> of updates.</p>
+</li>
+</ul>
</div>
</div>
<div class="sect2">
-<h3 id="CrossDataCenterReplication_CDCR_-APIEntryPoints_Monitoring_">API Entry Points (Monitoring)</h3>
-<div class="paragraph">
-<p><code>core/cdcr?action=QUEUES</code>: <a href="#CrossDataCenterReplication_CDCR_-QUEUES">Fetches statistics about the queue</a> for each replica and about the update logs. <code>core/cdcr?action=OPS</code>: <a href="#CrossDataCenterReplication_CDCR_-OPS">Fetches statistics about the replication performance</a> (operations per second) for each replica <code>core/cdcr?action=ERRORS</code>: <a href="#CrossDataCenterReplication_CDCR_-ERRORS">Fetches statistics and other information about replication errors</a> for each replica.</p>
+<h3 id="api-entry-points-monitoring">API Entry Points (Monitoring)</h3>
+<div class="ulist">
+<ul>
+<li>
+<p><code>core/cdcr?action=QUEUES</code>: <a href="#CrossDataCenterReplication_CDCR_-QUEUES">Fetches statistics about the queue</a> for each replica and about the update logs.</p>
+</li>
+<li>
+<p><code>core/cdcr?action=OPS</code>: <a href="#CrossDataCenterReplication_CDCR_-OPS">Fetches statistics about the replication performance</a> (operations per second) for each replica.</p>
+</li>
+<li>
+<p><code>core/cdcr?action=ERRORS</code>: <a href="#CrossDataCenterReplication_CDCR_-ERRORS">Fetches statistics and other information about replication errors</a> for each replica.</p>
+</li>
+</ul>
</div>
</div>
<div class="sect2">
-<h3 id="CrossDataCenterReplication_CDCR_-ControlCommands">Control Commands</h3>
+<h3 id="control-commands">Control Commands</h3>
<div class="sect3">
<h4 id="CrossDataCenterReplication_CDCR_-STATUS">STATUS</h4>
<div class="paragraph">
<p><code>/collection/cdcr?action=STATUS</code></p>
</div>
-<div class="paragraph">
-<p><strong>Input</strong></p>
-</div>
+<div class="sect4">
+<h5 id="input">Input</h5>
<div class="paragraph">
<p><strong>Query Parameters:</strong> There are no parameters to this command.</p>
</div>
-<div class="paragraph">
-<p><strong>Output</strong></p>
</div>
+<div class="sect4">
+<h5 id="output">Output</h5>
<div class="paragraph">
<p><strong>Output Content</strong></p>
</div>
<div class="paragraph">
<p>The current state of the CDCR, which includes the state of the replication process and the state of the buffer.</p>
</div>
-<div class="paragraph">
-<p><strong>Examples</strong></p>
</div>
+<div class="sect4">
+<h5 id="a-id-cdcr_examples-a-examples"><a id="cdcr_examples"></a>Examples</h5>
<div class="paragraph">
-<p><strong>Input</strong>: There are no parameters to this command.</p>
+<p><strong>Input</strong></p>
</div>
<div class="listingblock">
<div class="content">
-<pre class="pygments highlight"><code data-lang="java"> http<span style="color: #666666">:</span><span style="color: #408080; font-style: italic">//host:8983/solr/<collection_name>/cdcr?action=STATUS</span></code></pre>
+<pre class="pygments highlight"><code data-lang="text"> http://host:8983/solr/<collection_name>/cdcr?action=STATUS</code></pre>
</div>
</div>
<div class="paragraph">
@@ -1844,16 +1891,17 @@ $('#toc').on('click', 'a', function() {
</div>
<div class="listingblock">
<div class="content">
-<pre class="pygments highlight"><code data-lang="java"><span style="color: #666666">{</span>
- <span style="color: #BA2121">"responseHeader"</span><span style="color: #666666">:</span> <span style="color: #666666">{</span>
- <span style="color: #BA2121">"status"</span><span style="color: #666666">:</span> <span style="color: #666666">0,</span>
- <span style="color: #BA2121">"QTime"</span><span style="color: #666666">:</span> <span style="color: #666666">0</span>
- <span style="color: #666666">},</span>
- <span style="color: #BA2121">"status"</span><span style="color: #666666">:</span> <span style="color: #666666">{</span>
- <span style="color: #BA2121">"process"</span><span style="color: #666666">:</span> <span style="color: #BA2121">"stopped"</span><span style="color: #666666">,</span>
- <span style="color: #BA2121">"buffer"</span><span style="color: #666666">:</span> <span style="color: #BA2121">"enabled"</span>
- <span style="color: #666666">}</span>
-<span style="color: #666666">}</span></code></pre>
+<pre class="pygments highlight"><code data-lang="json">{
+ <span style="color: #008000; font-weight: bold">"responseHeader"</span>: {
+ <span style="color: #008000; font-weight: bold">"status"</span>: <span style="color: #666666">0</span>,
+ <span style="color: #008000; font-weight: bold">"QTime"</span>: <span style="color: #666666">0</span>
+ },
+ <span style="color: #008000; font-weight: bold">"status"</span>: {
+ <span style="color: #008000; font-weight: bold">"process"</span>: <span style="color: #BA2121">"stopped"</span>,
+ <span style="color: #008000; font-weight: bold">"buffer"</span>: <span style="color: #BA2121">"enabled"</span>
+ }
+}</code></pre>
+</div>
</div>
</div>
</div>
@@ -1862,30 +1910,29 @@ $('#toc').on('click', 'a', function() {
<div class="paragraph">
<p><code>/collection/cdcr?action=ENABLEBUFFER</code></p>
</div>
-<div class="paragraph">
-<p><strong>Input</strong></p>
-</div>
+<div class="sect4">
+<h5 id="input-2">Input</h5>
<div class="paragraph">
<p><strong>Query Parameters:</strong> There are no parameters to this command.</p>
</div>
-<div class="paragraph">
-<p><strong>Output</strong></p>
</div>
+<div class="sect4">
+<h5 id="output-2">Output</h5>
<div class="paragraph">
<p><strong>Output Content</strong></p>
</div>
<div class="paragraph">
<p>The status of the process and an indication of whether the buffer is enabled</p>
</div>
-<div class="paragraph">
-<p><strong>Examples</strong></p>
</div>
+<div class="sect4">
+<h5 id="examples">Examples</h5>
<div class="paragraph">
-<p><strong>Input</strong> This command enables the buffer, there are no parameters.</p>
+<p><strong>Input</strong></p>
</div>
<div class="listingblock">
<div class="content">
-<pre class="pygments highlight"><code data-lang="java"> http<span style="color: #666666">:</span><span style="color: #408080; font-style: italic">//host:8983/solr/<collection_name>/cdcr?action=ENABLEBUFFER</span></code></pre>
+<pre class="pygments highlight"><code data-lang="text"> http://host:8983/solr/<collection_name>/cdcr?action=ENABLEBUFFER</code></pre>
</div>
</div>
<div class="paragraph">
@@ -1893,16 +1940,17 @@ $('#toc').on('click', 'a', function() {
</div>
<div class="listingblock">
<div class="content">
-<pre class="pygments highlight"><code data-lang="java"><span style="color: #666666">{</span>
- <span style="color: #BA2121">"responseHeader"</span><span style="color: #666666">:</span> <span style="color: #666666">{</span>
- <span style="color: #BA2121">"status"</span><span style="color: #666666">:</span> <span style="color: #666666">0,</span>
- <span style="color: #BA2121">"QTime"</span><span style="color: #666666">:</span> <span style="color: #666666">0</span>
- <span style="color: #666666">},</span>
- <span style="color: #BA2121">"status"</span><span style="color: #666666">:</span> <span style="color: #666666">{</span>
- <span style="color: #BA2121">"process"</span><span style="color: #666666">:</span> <span style="color: #BA2121">"started"</span><span style="color: #666666">,</span>
- <span style="color: #BA2121">"buffer"</span><span style="color: #666666">:</span> <span style="color: #BA2121">"enabled"</span>
- <span style="color: #666666">}</span>
-<span style="color: #666666">}</span></code></pre>
+<pre class="pygments highlight"><code data-lang="json">{
+ <span style="color: #008000; font-weight: bold">"responseHeader"</span>: {
+ <span style="color: #008000; font-weight: bold">"status"</span>: <span style="color: #666666">0</span>,
+ <span style="color: #008000; font-weight: bold">"QTime"</span>: <span style="color: #666666">0</span>
+ },
+ <span style="color: #008000; font-weight: bold">"status"</span>: {
+ <span style="color: #008000; font-weight: bold">"process"</span>: <span style="color: #BA2121">"started"</span>,
+ <span style="color: #008000; font-weight: bold">"buffer"</span>: <span style="color: #BA2121">"enabled"</span>
+ }
+}</code></pre>
+</div>
</div>
</div>
</div>
@@ -1911,44 +1959,44 @@ $('#toc').on('click', 'a', function() {
<div class="paragraph">
<p><code>/collection/cdcr?action=DISABLEBUFFER</code></p>
</div>
-<div class="paragraph">
-<p><strong>Input</strong></p>
-</div>
+<div class="sect4">
+<h5 id="input-3">Input</h5>
<div class="paragraph">
<p><strong>Query Parameters:</strong> There are no parameters to this command</p>
</div>
-<div class="paragraph">
-<p><strong>Output</strong></p>
</div>
+<div class="sect4">
+<h5 id="output-3">Output</h5>
<div class="paragraph">
<p><strong>Output Content:</strong> The status of CDCR and an indication that the buffer is disabled.</p>
</div>
-<div class="paragraph">
-<p><strong>Examples</strong></p>
</div>
+<div class="sect4">
+<h5 id="examples-2">Examples</h5>
<div class="paragraph">
-<p><strong>Input:</strong> This command disables buffering</p>
+<p><strong>Input</strong></p>
</div>
<div class="listingblock">
<div class="content">
-<pre class="pygments highlight"><code data-lang="java"><span style="color: #A0A000">http:</span><span style="color: #408080; font-style: italic">//host:8983/solr/<collection_name>/cdcr?action=DISABLEBUFFER</span></code></pre>
+<pre class="pygments highlight"><code data-lang="text">http://host:8983/solr/<collection_name>/cdcr?action=DISABLEBUFFER</code></pre>
</div>
</div>
<div class="paragraph">
-<p><strong>Output:</strong> The status of CDCR and an indication that the buffer is disabled.</p>
+<p><strong>Output</strong></p>
</div>
<div class="listingblock">
<div class="content">
-<pre class="pygments highlight"><code data-lang="java"><span style="color: #666666">{</span>
- <span style="color: #BA2121">"responseHeader"</span><span style="color: #666666">:</span> <span style="color: #666666">{</span>
- <span style="color: #BA2121">"status"</span><span style="color: #666666">:</span> <span style="color: #666666">0,</span>
- <span style="color: #BA2121">"QTime"</span><span style="color: #666666">:</span> <span style="color: #666666">0</span>
- <span style="color: #666666">},</span>
- <span style="color: #BA2121">"status"</span><span style="color: #666666">:</span> <span style="color: #666666">{</span>
- <span style="color: #BA2121">"process"</span><span style="color: #666666">:</span> <span style="color: #BA2121">"started"</span><span style="color: #666666">,</span>
- <span style="color: #BA2121">"buffer"</span><span style="color: #666666">:</span> <span style="color: #BA2121">"disabled"</span>
- <span style="color: #666666">}</span>
-<span style="color: #666666">}</span></code></pre>
+<pre class="pygments highlight"><code data-lang="json">{
+ <span style="color: #008000; font-weight: bold">"responseHeader"</span>: {
+ <span style="color: #008000; font-weight: bold">"status"</span>: <span style="color: #666666">0</span>,
+ <span style="color: #008000; font-weight: bold">"QTime"</span>: <span style="color: #666666">0</span>
+ },
+ <span style="color: #008000; font-weight: bold">"status"</span>: {
+ <span style="color: #008000; font-weight: bold">"process"</span>: <span style="color: #BA2121">"started"</span>,
+ <span style="color: #008000; font-weight: bold">"buffer"</span>: <span style="color: #BA2121">"disabled"</span>
+ }
+}</code></pre>
+</div>
</div>
</div>
</div>
@@ -1957,27 +2005,26 @@ $('#toc').on('click', 'a', function() {
<div class="paragraph">
<p><code>/collection/cdcr?action=START</code></p>
</div>
-<div class="paragraph">
-<p><strong>Input</strong></p>
-</div>
+<div class="sect4">
+<h5 id="input-4">Input</h5>
<div class="paragraph">
<p><strong>Query Parameters:</strong> There are no parameters for this action</p>
</div>
-<div class="paragraph">
-<p><strong>Output</strong></p>
</div>
+<div class="sect4">
+<h5 id="output-4">Output</h5>
<div class="paragraph">
<p><strong>Output Content:</strong> Confirmation that CDCR is started and the status of buffering</p>
</div>
-<div class="paragraph">
-<p><strong>Examples</strong></p>
</div>
+<div class="sect4">
+<h5 id="examples-3">Examples</h5>
<div class="paragraph">
<p><strong>Input</strong></p>
</div>
<div class="listingblock">
<div class="content">
-<pre class="pygments highlight"><code data-lang="java"><span style="color: #A0A000">http:</span><span style="color: #408080; font-style: italic">//host:8983/solr/<collection_name>/cdcr?action=START</span></code></pre>
+<pre class="pygments highlight"><code data-lang="text">http://host:8983/solr/<collection_name>/cdcr?action=START</code></pre>
</div>
</div>
<div class="paragraph">
@@ -1985,16 +2032,17 @@ $('#toc').on('click', 'a', function() {
</div>
<div class="listingblock">
<div class="content">
-<pre class="pygments highlight"><code data-lang="java"><span style="color: #666666">{</span>
- <span style="color: #BA2121">"responseHeader"</span><span style="color: #666666">:</span> <span style="color: #666666">{</span>
- <span style="color: #BA2121">"status"</span><span style="color: #666666">:</span> <span style="color: #666666">0,</span>
- <span style="color: #BA2121">"QTime"</span><span style="color: #666666">:</span> <span style="color: #666666">0</span>
- <span style="color: #666666">},</span>
- <span style="color: #BA2121">"status"</span><span style="color: #666666">:</span> <span style="color: #666666">{</span>
- <span style="color: #BA2121">"process"</span><span style="color: #666666">:</span> <span style="color: #BA2121">"started"</span><span style="color: #666666">,</span>
- <span style="color: #BA2121">"buffer"</span><span style="color: #666666">:</span> <span style="color: #BA2121">"enabled"</span>
- <span style="color: #666666">}</span>
-<span style="color: #666666">}</span></code></pre>
+<pre class="pygments highlight"><code data-lang="json">{
+ <span style="color: #008000; font-weight: bold">"responseHeader"</span>: {
+ <span style="color: #008000; font-weight: bold">"status"</span>: <span style="color: #666666">0</span>,
+ <span style="color: #008000; font-weight: bold">"QTime"</span>: <span style="color: #666666">0</span>
+ },
+ <span style="color: #008000; font-weight: bold">"status"</span>: {
+ <span style="color: #008000; font-weight: bold">"process"</span>: <span style="color: #BA2121">"started"</span>,
+ <span style="color: #008000; font-weight: bold">"buffer"</span>: <span style="color: #BA2121">"enabled"</span>
+ }
+}</code></pre>
+</div>
</div>
</div>
</div>
@@ -2003,27 +2051,26 @@ $('#toc').on('click', 'a', function() {
<div class="paragraph">
<p><code>/collection/cdcr?action=STOP</code></p>
</div>
-<div class="paragraph">
-<p><strong>Input</strong></p>
-</div>
+<div class="sect4">
+<h5 id="input-5">Input</h5>
<div class="paragraph">
<p><strong>Query Parameters:</strong> There are no parameters for this command.</p>
</div>
-<div class="paragraph">
-<p><strong>Output</strong></p>
</div>
+<div class="sect4">
+<h5 id="output-5">Output</h5>
<div class="paragraph">
<p><strong>Output Content:</strong> The status of CDCR, including the confirmation that CDCR is stopped</p>
</div>
-<div class="paragraph">
-<p><strong>Examples</strong></p>
</div>
+<div class="sect4">
+<h5 id="examples-4">Examples</h5>
<div class="paragraph">
<p><strong>Input</strong></p>
</div>
<div class="listingblock">
<div class="content">
-<pre class="pygments highlight"><code data-lang="java"> http<span style="color: #666666">:</span><span style="color: #408080; font-style: italic">//host:8983/solr/<collection_name>/cdcr?action=STOP</span></code></pre>
+<pre class="pygments highlight"><code data-lang="text"> http://host:8983/solr/<collection_name>/cdcr?action=STOP</code></pre>
</div>
</div>
<div class="paragraph">
@@ -2031,16 +2078,17 @@ $('#toc').on('click', 'a', function() {
</div>
<div class="listingblock">
<div class="content">
-<pre class="pygments highlight"><code data-lang="java"><span style="color: #666666">{</span>
- <span style="color: #BA2121">"responseHeader"</span><span style="color: #666666">:</span> <span style="color: #666666">{</span>
- <span style="color: #BA2121">"status"</span><span style="color: #666666">:</span> <span style="color: #666666">0,</span>
- <span style="color: #BA2121">"QTime"</span><span style="color: #666666">:</span> <span style="color: #666666">0</span>
- <span style="color: #666666">},</span>
- <span style="color: #BA2121">"status"</span><span style="color: #666666">:</span> <span style="color: #666666">{</span>
- <span style="color: #BA2121">"process"</span><span style="color: #666666">:</span> <span style="color: #BA2121">"stopped"</span><span style="color: #666666">,</span>
- <span style="color: #BA2121">"buffer"</span><span style="color: #666666">:</span> <span style="color: #BA2121">"enabled"</span>
- <span style="color: #666666">}</span>
-<span style="color: #666666">}</span></code></pre>
+<pre class="pygments highlight"><code data-lang="json">{
+ <span style="color: #008000; font-weight: bold">"responseHeader"</span>: {
+ <span style="color: #008000; font-weight: bold">"status"</span>: <span style="color: #666666">0</span>,
+ <span style="color: #008000; font-weight: bold">"QTime"</span>: <span style="color: #666666">0</span>
+ },
+ <span style="color: #008000; font-weight: bold">"status"</span>: {
+ <span style="color: #008000; font-weight: bold">"process"</span>: <span style="color: #BA2121">"stopped"</span>,
+ <span style="color: #008000; font-weight: bold">"buffer"</span>: <span style="color: #BA2121">"enabled"</span>
+ }
+}</code></pre>
+</div>
</div>
</div>
</div>
@@ -2052,33 +2100,32 @@ $('#toc').on('click', 'a', function() {
<div class="paragraph">
<p><code>/core/cdcr?action=QUEUES</code></p>
</div>
-<div class="paragraph">
-<p><strong>Input</strong></p>
-</div>
+<div class="sect4">
+<h5 id="input-6">Input</h5>
<div class="paragraph">
<p><strong>Query Parameters:</strong> There are no parameters for this command</p>
</div>
-<div class="paragraph">
-<p><strong>Output</strong></p>
</div>
+<div class="sect4">
+<h5 id="output-6">Output</h5>
<div class="paragraph">
<p><strong>Output Content</strong></p>
</div>
<div class="paragraph">
-<p>The output is composed of a list âqueuesâ which contains a list of (ZooKeeper) Target hosts, themselves containing a list of Target collections. For each collection, the current size of the queue and the timestamp of the last update operation successfully processed is provided. The timestamp of the update operation is the original timestamp, i.e., the time this operation was processed on the Source SolrCloud. This allows an estimate the latency of the replication process.</p>
+<p>The output is composed of a list âqueuesâ which contains a list of (ZooKeeper) target hosts, themselves containing a list of target collections. For each collection, the current size of the queue and the timestamp of the last update operation successfully processed is provided. The timestamp of the update operation is the original timestamp, i.e., the time this operation was processed on the Source SolrCloud. This allows an estimate the latency of the replication process.</p>
</div>
<div class="paragraph">
<p>The âqueuesâ object also contains information about the updates log, such as the size (in bytes) of the updates log on disk (âtlogTotalSizeâ), the number of transaction log files (âtlogTotalCountâ) and the status of the updates log synchronizer (âupdateLogSynchronizerâ).</p>
</div>
-<div class="paragraph">
-<p><strong>Examples</strong></p>
</div>
+<div class="sect4">
+<h5 id="examples-5">Examples</h5>
<div class="paragraph">
<p><strong>Input</strong></p>
</div>
<div class="listingblock">
<div class="content">
-<pre class="pygments highlight"><code data-lang="java"> http<span style="color: #666666">:</span><span style="color: #408080; font-style: italic">//host:8983/solr/<replica_name>/cdcr?action=QUEUES</span></code></pre>
+<pre class="pygments highlight"><code data-lang="text"> http://host:8983/solr/<replica_name>/cdcr?action=QUEUES</code></pre>
</div>
</div>
<div class="paragraph">
@@ -2086,23 +2133,24 @@ $('#toc').on('click', 'a', function() {
</div>
<div class="listingblock">
<div class="content">
-<pre class="pygments highlight"><code data-lang="java"><span style="color: #666666">{</span>
- responseHeader<span style="color: #666666">={</span>
- status<span style="color: #666666">=0,</span>
- QTime<span style="color: #666666">=1</span>
- <span style="color: #666666">},</span>
- queues<span style="color: #666666">={</span>
- <span style="color: #666666">127.0.0.1:</span> <span style="color: #666666">40342/</span>solr<span style="color: #666666">={</span>
- Target_collection<span style="color: #666666">={</span>
- queueSize<span style="color: #666666">=104,</span>
- lastTimestamp<span style="color: #666666">=2014-12-02</span>T10<span style="color: #666666">:</span> <span style="color: #666666">32:</span> <span style="color: #666666">15.879</span>Z
- <span style="color: #666666">}</span>
- <span style="color: #666666">}</span>
- <span style="color: #666666">},</span>
- tlogTotalSize<span style="color: #666666">=3817,</span>
- tlogTotalCount<span style="color: #666666">=1,</span>
- updateLogSynchronizer<span style="color: #666666">=</span>stopped
-<span style="color: #666666">}</span></code></pre>
+<pre class="pygments highlight"><code data-lang="json">{
+ <span style="color: #008000; font-weight: bold">"responseHeader"</span>:{
+ <span style="color: #008000; font-weight: bold">"status"</span>: <span style="color: #666666">0</span>,
+ <span style="color: #008000; font-weight: bold">"QTime"</span>: <span style="color: #666666">1</span>
+ },
+ <span style="color: #008000; font-weight: bold">"queues"</span>:{
+ <span style="color: #008000; font-weight: bold">"127.0.0.1: 40342/solr"</span>:{
+ <span style="color: #008000; font-weight: bold">"Target_collection"</span>:{
+ <span style="color: #008000; font-weight: bold">"queueSize"</span>: <span style="color: #666666">104</span>,
+ <span style="color: #008000; font-weight: bold">"lastTimestamp"</span>: <span style="color: #BA2121">"2014-12-02T10:32:15.879Z"</span>
+ }
+ }
+ },
+ <span style="color: #008000; font-weight: bold">"tlogTotalSize"</span>:<span style="color: #666666">3817</span>,
+ <span style="color: #008000; font-weight: bold">"tlogTotalCount"</span>:<span style="color: #666666">1</span>,
+ <span style="color: #008000; font-weight: bold">"updateLogSynchronizer"</span>: <span style="color: #BA2121">"stopped"</span>
+}</code></pre>
+</div>
</div>
</div>
</div>
@@ -2111,27 +2159,26 @@ $('#toc').on('click', 'a', function() {
<div class="paragraph">
<p><code>/core/cdcr?action=OPS</code></p>
</div>
-<div class="paragraph">
-<p><strong>Input</strong></p>
-</div>
+<div class="sect4">
+<h5 id="input-7">Input</h5>
<div class="paragraph">
<p><strong>Query Parameters:</strong> There are no parameters for this command.</p>
</div>
-<div class="paragraph">
-<p><strong>Output</strong></p>
</div>
+<div class="sect4">
+<h5 id="output-7">Output</h5>
<div class="paragraph">
-<p><strong>Output Content:</strong> The output is composed of a list âoperationsPerSecondâ which contains a list of (ZooKeeper) Target hosts, themselves containing a list of Target collections. For each collection, the average number of processed operations per second since the start of the replication process is provided. The operations are further broken down into two groups: add and delete operations.</p>
+<p><strong>Output Content:</strong> The output is composed of a list âoperationsPerSecondâ which contains a list of (ZooKeeper) target hosts, themselves containing a list of target collections. For each collection, the average number of processed operations per second since the start of the replication process is provided. The operations are further broken down into two groups: add and delete operations.</p>
</div>
-<div class="paragraph">
-<p><strong>Examples</strong></p>
</div>
+<div class="sect4">
+<h5 id="examples-6">Examples</h5>
<div class="paragraph">
<p><strong>Input</strong></p>
</div>
<div class="listingblock">
<div class="content">
-<pre class="pygments highlight"><code data-lang="java"> http<span style="color: #666666">:</span><span style="color: #408080; font-style: italic">//host:8983/solr/<collection_name>/cdcr?action=OPS</span></code></pre>
+<pre class="pygments highlight"><code data-lang="text"> http://host:8983/solr/<collection_name>/cdcr?action=OPS</code></pre>
</div>
</div>
<div class="paragraph">
@@ -2139,21 +2186,22 @@ $('#toc').on('click', 'a', function() {
</div>
<div class="listingblock">
<div class="content">
-<pre class="pygments highlight"><code data-lang="java"><span style="color: #666666">{</span>
- responseHeader<span style="color: #666666">={</span>
- status<span style="color: #666666">=0,</span>
- QTime<span style="color: #666666">=1</span>
- <span style="color: #666666">},</span>
- operationsPerSecond<span style="color: #666666">={</span>
- <span style="color: #666666">127.0.0.1:</span> <span style="color: #666666">59661/</span>solr<span style="color: #666666">={</span>
- Target_collection<span style="color: #666666">={</span>
- all<span style="color: #666666">=297.102944952749052,</span>
- adds<span style="color: #666666">=297.102944952749052,</span>
- deletes<span style="color: #666666">=0.0</span>
- <span style="color: #666666">}</span>
- <span style="color: #666666">}</span>
- <span style="color: #666666">}</span>
-<span style="color: #666666">}</span></code></pre>
+<pre class="pygments highlight"><code data-lang="json">{
+ <span style="color: #008000; font-weight: bold">"responseHeader"</span>:{
+ <span style="color: #008000; font-weight: bold">"status"</span>:<span style="color: #666666">0</span>,
+ <span style="color: #008000; font-weight: bold">"QTime"</span>:<span style="color: #666666">1</span>
+ },
+ <span style="color: #008000; font-weight: bold">"operationsPerSecond"</span>:{
+ <span style="color: #008000; font-weight: bold">"127.0.0.1: 59661/solr"</span>:{
+ <span style="color: #008000; font-weight: bold">"Target_collection"</span>:{
+ <span style="color: #008000; font-weight: bold">"all"</span>: <span style="color: #666666">297.102944952749052</span>,
+ <span style="color: #008000; font-weight: bold">"adds"</span>: <span style="color: #666666">297.102944952749052</span>,
+ <span style="color: #008000; font-weight: bold">"deletes"</span>: <span style="color: #666666">0.0</span>
+ }
+ }
+ }
+}</code></pre>
+</div>
</div>
</div>
</div>
@@ -2162,27 +2210,26 @@ $('#toc').on('click', 'a', function() {
<div class="paragraph">
<p><code>/core/cdcr?action=ERRORS</code></p>
</div>
-<div class="paragraph">
-<p><strong>Input</strong></p>
-</div>
+<div class="sect4">
+<h5 id="input-8">Input</h5>
<div class="paragraph">
<p><strong>Query Parameters:</strong> There are no parameters for this command.</p>
</div>
-<div class="paragraph">
-<p><strong>Output</strong></p>
</div>
+<div class="sect4">
+<h5 id="output-8">Output</h5>
<div class="paragraph">
-<p><strong>Output Content:</strong> The output is composed of a list âerrorsâ which contains a list of (ZooKeeper) Target hosts, themselves containing a list of Target collections. For each collection, information about errors encountered during the replication is provided, such as the number of consecutive errors encountered by the replicator thread, the number of bad requests or internal errors since the start of the replication process, and a list of the last errors encountered ordered by timestamp.</p>
+<p><strong>Output Content:</strong> The output is composed of a list âerrorsâ which contains a list of (ZooKeeper) target hosts, themselves containing a list of target collections. For each collection, information about errors encountered during the replication is provided, such as the number of consecutive errors encountered by the replicator thread, the number of bad requests or internal errors since the start of the replication process, and a list of the last errors encountered ordered by timestamp.</p>
</div>
-<div class="paragraph">
-<p><strong>Examples</strong></p>
</div>
+<div class="sect4">
+<h5 id="examples-7">Examples</h5>
<div class="paragraph">
<p><strong>Input</strong></p>
</div>
<div class="listingblock">
<div class="content">
-<pre class="pygments highlight"><code data-lang="java"> http<span style="color: #666666">:</span><span style="color: #408080; font-style: italic">//host:8983/solr/<collection_name>/cdcr?action=ERRORS</span></code></pre>
+<pre class="pygments highlight"><code data-lang="text"> http://host:8983/solr/<collection_name>/cdcr?action=ERRORS</code></pre>
</div>
</div>
<div class="paragraph">
@@ -2190,26 +2237,27 @@ $('#toc').on('click', 'a', function() {
</div>
<div class="listingblock">
<div class="content">
-<pre class="pygments highlight"><code data-lang="java"><span style="color: #666666">{</span>
- responseHeader<span style="color: #666666">={</span>
- status<span style="color: #666666">=0,</span>
- QTime<span style="color: #666666">=2</span>
- <span style="color: #666666">},</span>
- errors<span style="color: #666666">={</span>
- <span style="color: #666666">127.0.0.1:</span> <span style="color: #666666">36872/</span>solr<span style="color: #666666">={</span>
- Target_collection<span style="color: #666666">={</span>
- consecutiveErrors<span style="color: #666666">=3,</span>
- bad_request<span style="color: #666666">=0,</span>
- internal<span style="color: #666666">=3,</span>
- last<span style="color: #666666">={</span>
- <span style="color: #666666">2014-12-02</span>T11<span style="color: #666666">:</span> <span style="color: #666666">04:</span> <span style="color: #666666">42.523</span>Z<span style="color: #666666">=</span>internal<span style="color: #666666">,</span>
- <span style="color: #666666">2014-12-02</span>T11<span style="color: #666666">:</span> <span style="color: #666666">04:</span> <span style="color: #666666">39.223</span>Z<span style="color: #666666">=</span>internal<span style="color: #666666">,</span>
- <span style="color: #666666">2014-12-02</span>T11<span style="color: #666666">:</span> <span style="color: #666666">04:</span> <span style="color: #666666">38.22</span>Z<span style="color: #666666">=</span>internal
- <span style="color: #666666">}</span>
- <span style="color: #666666">}</span>
- <span style="color: #666666">}</span>
- <span style="color: #666666">}</span>
-<span style="color: #666666">}</span></code></pre>
+<pre class="pygments highlight"><code data-lang="json">{
+ <span style="color: #008000; font-weight: bold">"responseHeader"</span>:{
+ <span style="color: #008000; font-weight: bold">"status"</span>:<span style="color: #666666">0</span>,
+ <span style="color: #008000; font-weight: bold">"QTime"</span>:<span style="color: #666666">2</span>
+ },
+ <span style="color: #008000; font-weight: bold">"errors"</span>: {
+ <span style="color: #008000; font-weight: bold">"127.0.0.1: 36872/solr"</span>:{
+ <span style="color: #008000; font-weight: bold">"Target_collection"</span>:{
+ <span style="color: #008000; font-weight: bold">"consecutiveErrors"</span>:<span style="color: #666666">3</span>,
+ <span style="color: #008000; font-weight: bold">"bad_request"</span>:<span style="color: #666666">0</span>,
+ <span style="color: #008000; font-weight: bold">"internal"</span>:<span style="color: #666666">3</span>,
+ <span style="color: #008000; font-weight: bold">"last"</span>:{
+ <span style="color: #008000; font-weight: bold">"2014-12-02T11:04:42.523Z"</span>:<span style="color: #BA2121">"internal"</span>,
+ <span style="color: #008000; font-weight: bold">"2014-12-02T11:04:39.223Z"</span>:<span style="color: #BA2121">"internal"</span>,
+ <span style="color: #008000; font-weight: bold">"2014-12-02T11:04:38.22Z"</span>:<span style="color: #BA2121">"internal"</span>
+ }
+ }
+ }
+ }
+}</code></pre>
+</div>
</div>
</div>
</div>
@@ -2217,28 +2265,31 @@ $('#toc').on('click', 'a', function() {
</div>
</div>
<div class="sect1">
-<h2 id="CrossDataCenterReplication_CDCR_-FirstTime">Initial Startup</h2>
+<h2 id="initial-startup">Initial Startup</h2>
<div class="sectionbody">
<div class="paragraph">
-<p>This is a general approach for initializing CDCR in a production environment based upon an approach taken by the initial working installation of CDCR and generously contributed to illustrate a "real world" scenario. NOTE: The configuration snippets below illustrate specific points of configuration.</p>
+<p>This is a general approach for initializing CDCR in a production environment based upon an approach taken by the initial working installation of CDCR and generously contributed to illustrate a "real world" scenario.</p>
</div>
<div class="ulist">
<ul>
<li>
-<p>Customer uses the CDCR approach to keep a remote DR instance available for production backup. This is an active-passive solution.</p>
+<p>Customer uses the CDCR approach to keep a remote disaster-recovery instance available for production backup. This is an active-passive solution.</p>
</li>
<li>
<p>Customer has 26 clouds with 200 million assets per cloud (15GB indexes). Total document count is over 4.8 billion.</p>
<div class="ulist">
<ul>
<li>
-<p>Source and Target clouds were synched in 2-3 hour maintenance windows to establish the base index for the Targets.</p>
+<p>Source and target clouds were synched in 2-3 hour maintenance windows to establish the base index for the targets.</p>
</li>
</ul>
</div>
</li>
-<li>
-<p>Tip: As usual, it is good to start small. Sync a single cloud and monitor for a period of time before doing the others. You may need to adjust your settings several times before finding the right balance.</p>
+</ul>
+</div>
+<div class="paragraph">
+<p>As usual, it is good to start small. Sync a single cloud and monitor for a period of time before doing the others. You may need to adjust your settings several times before finding the right balance.</p>
+</div>
<div class="ulist">
<ul>
<li>
@@ -2248,67 +2299,45 @@ $('#toc').on('click', 'a', function() {
<p>Stop the SolrCloud instances at the Source</p>
</li>
<li>
-<p>Include the cdcr request handler configuration in <code>solrconfig.xml</code></p>
-</li>
-</ul>
-</div>
-</li>
-</ul>
-</div>
+<p>Include the CDCR request handler configuration in <code>solrconfig.xml</code> as in the below example.</p>
<div class="listingblock">
<div class="content">
-<pre class="pygments highlight"><code data-lang="java"> http<span style="color: #666666">:</span><span style="color: #408080; font-style: italic">//localhost:898</span>
-<span style="color: #666666"><</span>requestHandler name<span style="color: #666666">=</span><span style="color: #BA2121">"/cdcr"</span> class<span style="color: #666666">=</span><span style="color: #BA2121">"solr.CdcrRequestHandler"</span><span style="color: #666666">></span>
- <span style="color: #666666"><</span>lst name<span style="color: #666666">=</span><span style="color: #BA2121">"replica"</span><span style="color: #666666">></span>
- <span style="color: #666666"><</span>str name<span style="color: #666666">=</span><span style="color: #BA2121">"zkHost"</span><span style="color: #666666">></span>$<span style="color: #666666">{</span>TargetZk<span style="color: #666666">}</</span>str<span style="color: #666666">></span>
- <span style="color: #666666"><</span>str name<span style="color: #666666">=</span><span style="color: #BA2121">"Source"</span><span style="color: #666666">></span>$<span style="color: #666666">{</span>SourceCollection<span style="color: #666666">}</</span>str<span style="color: #666666">></span>
- <span style="color: #666666"><</span>str name<span style="color: #666666">=</span><span style="color: #BA2121">"Target"</span><span style="color: #666666">></span>$<span style="color: #666666">{</span>TargetCollection<span style="color: #666666">}</</span>str<span style="color: #666666">></span>
- <span style="color: #666666"></</span>lst<span style="color: #666666">></span>
- <span style="color: #666666"><</span>lst name<span style="color: #666666">=</span><span style="color: #BA2121">"replicator"</span><span style="color: #666666">></span>
- <span style="color: #666666"><</span>str name<span style="color: #666666">=</span><span style="color: #BA2121">"threadPoolSize"</span><span style="color: #666666">>8</</span>str<span style="color: #666666">></span>
- <span style="color: #666666"><</span>str name<span style="color: #666666">=</span><span style="color: #BA2121">"schedule"</span><span style="color: #666666">>10</</span>str<span style="color: #666666">></span>
- <span style="color: #666666"><</span>str name<span style="color: #666666">=</span><span style="color: #BA2121">"batchSize"</span><span style="color: #666666">>2000</</span>str<span style="color: #666666">></span>
- <span style="color: #666666"></</span>lst<span style="color: #666666">></span>
- <span style="color: #666666"><</span>lst name<span style="color: #666666">=</span><span style="color: #BA2121">"updateLogSynchronizer"</span><span style="color: #666666">></span>
- <span style="color: #666666"><</span>str name<span style="color: #666666">=</span><span style="color: #BA2121">"schedule"</span><span style="color: #666666">>1000</</span>str<span style="color: #666666">></span>
- <span style="color: #666666"></</span>lst<span style="color: #666666">></span>
- <span style="color: #666666"></</span>requestHandler<span style="color: #666666">></span>
+<pre class="pygments highlight"><code data-lang="xml"><span style="color: #008000; font-weight: bold"><requestHandler</span> <span style="color: #7D9029">name=</span><span style="color: #BA2121">"/cdcr"</span> <span style="color: #7D9029">class=</span><span style="color: #BA2121">"solr.CdcrRequestHandler"</span><span style="color: #008000; font-weight: bold">></span>
+ <span style="color: #008000; font-weight: bold"><lst</span> <span style="color: #7D9029">name=</span><span style="color: #BA2121">"replica"</span><span style="color: #008000; font-weight: bold">></span>
+ <span style="color: #008000; font-weight: bold"><str</span> <span style="color: #7D9029">name=</span><span style="color: #BA2121">"zkHost"</span><span style="color: #008000; font-weight: bold">></span>${TargetZk}<span style="color: #008000; font-weight: bold"></str></span>
+ <span style="color: #008000; font-weight: bold"><str</span> <span style="color: #7D9029">name=</span><span style="color: #BA2121">"Source"</span><span style="color: #008000; font-weight: bold">></span>${SourceCollection}<span style="color: #008000; font-weight: bold"></str></span>
+ <span style="color: #008000; font-weight: bold"><str</span> <span style="color: #7D9029">name=</span><span style="color: #BA2121">"Target"</span><span style="color: #008000; font-weight: bold">></span>${TargetCollection}<span style="color: #008000; font-weight: bold"></str></span>
+ <span style="color: #008000; font-weight: bold"></lst></span>
+ <span style="color: #008000; font-weight: bold"><lst</span> <span style="color: #7D9029">name=</span><span style="color: #BA2121">"replicator"</span><span style="color: #008000; font-weight: bold">></span>
+ <span style="color: #008000; font-weight: bold"><str</span> <span style="color: #7D9029">name=</span><span style="color: #BA2121">"threadPoolSize"</span><span style="color: #008000; font-weight: bold">></span>8<span style="color: #008000; font-weight: bold"></str></span>
+ <span style="color: #008000; font-weight: bold"><str</span> <span style="color: #7D9029">name=</span><span style="color: #BA2121">"schedule"</span><span style="color: #008000; font-weight: bold">></span>10<span style="color: #008000; font-weight: bold"></str></span>
+ <span style="color: #008000; font-weight: bold"><str</span> <span style="color: #7D9029">name=</span><span style="color: #BA2121">"batchSize"</span><span style="color: #008000; font-weight: bold">></span>2000<span style="color: #008000; font-weight: bold"></str></span>
+ <span style="color: #008000; font-weight: bold"></lst></span>
+ <span style="color: #008000; font-weight: bold"><lst</span> <span style="color: #7D9029">name=</span><span style="color: #BA2121">"updateLogSynchronizer"</span><span style="color: #008000; font-weight: bold">></span>
[... 225 lines stripped ...]