Open Couchbase Web Console and login. This is the administrative user interface for Couchbase Server. For more information, see Couchbase Server Manual.

Click on the XDCR tab. Under this tab you can configure and start data replication between a source and destination cluster. In this case our source cluster is a Couchbase cluster and the destination is Elasticsearch.

Click on Create Cluster Reference.

A panel will appear where you can specify information for your Elasticsearch cluster. This is the Elasticsearch cluster where Couchbase Server will send copies of documents from a databucket to be indexed.

Enter a name, hostname, username and password for your Elasticsesarch cluster then click Save. Be aware that Elasticsearch will be listening on port 9091 which is not a standard port for those familiar with Couchbase Server.

Figure 3.1. Create Reference for Replication

The reference to the new replication will appear in the Remote Clusters list under the XDCR Tab.

To set up replication, click Create Replication.

A panel appears where you can establish replication from your Couchbase cluster to Elasticsearch.

Under Replicate changes from: Bucket, choose beer-sample.

Under the section To: select ElasticSearch.

For Bucket: enter beer-sample. This is actually the Elasticsearch index where the data will be sent for indexing.

Finally click Replicate to start replication of documents to Elasticsearch. Couchbase Server will begin sending data from the beer-sample bucket to your Elasticsearch cluster.

Figure 3.2. Create Reference for Replication

Under the Ongoing Replications section, you will see the replication and status of replication.

You can also view the data transfer by clicking the Overview tab of Elasticsearch head:

Figure 3.3. View Replication

The docs field indicates the number of items that have been indexed by Elasticsearch. At this point you can begin querying data from Elasticsearch.

Note that the number of documents displayed by Elasticsearch head may be greater than the actual number of documents in Couchbase Server. This is because XDCR and the Couchbase Plug-in for Elasticsearch will also send additional documents that describe the status of replication and Elasticsearch head will show this total number. There is an alternate, more accurate way you can determine the true number of documents indexed by Elasticsearch, which excludes extra status documents. You can use this method to debug possible data transfer issues between Couchbase and Elasticsearch. For more information, see Chapter 4, Monitoring and Troubleshooting, Compare Document Count.