Apache Solr Reference Guide Covering Apache Solr 6.0

http://host:port/solr/collection_name/cdcr?action=DISABLEBUFFER
Renable indexing
Monitoring
1.
2.
Network and disk space monitoring are essential. Ensure that the system has plenty of available storage
to queue up changes if there is a disconnect between the Source and Target. A network outage between
the two data centers can cause your disk usage to grow.
a.
Tip: Set a monitor for your disks to send alerts when the disk gets over a certain percentage (eg.
70%)
b. Tip: Run a test. With moderate indexing, how long can the system queue changes before you run
out of disk space?
Create a simple way to check the counts between the Source and the Target.
a.
Keep in mind that if indexing is running, the Source and Target may not match document for
document. Set an alert to fire if the difference is greater than some percentage of the overall cloud
size.
ZooKeeper settings
1.
With CDCR, the Target ZooKeepers will have connections from the Target clouds and the Source clouds.
You may need to increase the maxClientCnxns setting in the zoo.cfg.
## set numbers of connection to 200 from client
## is maxClientCnxns=0 that means no limit
maxClientCnxns=800
Upgrading and Patching Production
1.
When rolling in upgrades to your indexer or application, you should shutdown the Source (production) and
the Target (DR). Depending on your setup, you may want to pause/stop indexing. Deploy the release or
patch and renable indexing. Then start the Target (DR).
a. Tip: There is no need to reissue the DISABLEBUFFERS or START commands. These are
persisted.
b. Tip: After starting the Target, run a simple test. Add a test document to each of the Source clouds.
Then check for it on the Target.
#send to the Source
curl http:///solr/cloud1/update -H 'Content-type:application/json' -d
'[{"SKU":"ABC"}]'
#check the Target
curl "http://:8983/solr/cloud1/select?q=SKU:ABC&wt=json&indent=true"
Apache Solr Reference Guide 6.0
624