Purpose

Request: To take the Punjab W&S ERP elasticsearch index and restore it on Punjab Rainmaker elasticsearch cluster.

Environment: Punjab W&S ERP elasticsearch (Production), Punjab Rainmaker elasticsearch cluster (UAT)

Elasticsearch Indices needs to dump:

1. receipts-consumers
2. demandbillconsumers
3. waterchargesconsumers
4. projecteddemand-consumers
5. applications-receipts
6. pwssbulbs
7. seweragechargesconsumers
8. wsapplications
9. nonpwssbulbs
10. dwssulbs

Problem Statement

To take the Punjab W&S ERP elasticsearch index and restore it on Punjab Rainmaker elasticsearch cluster.

Solution Approach

1. From Punjab W&S ERP elasticsearch cluster, taken snaphots of 10 indecies using curl.
2. Pushed taken snapshots from the server to egov-aws s3 bucket.

Approach-1:

1. Trying to restore the snapshot from s3 bucket to Punjab Rainmaker elasticsearch cluster (UAT).
2. First locally by setting up elasticsearch cluster using minikube, here we are trying to push the elasticsearch snaphots taken to the es cluster.
3. Rainmaker UAT es cluster has, client, data, and master nodes.
4. Realized that es cluster (master,data,client) doesn't have a shared resource or filesystem to push the dump from locally or from s3

Approach-2:

5. Decided to use elasticdump an npm tool this will help in doing index to index dumping
6. elasticdump --input=http://<erp-elasticsearch-endpoint>/<index> --output=http://<rm-elasticsearch-client-endpoint>:9200/index

Conclusion 

From this using elasticdump command we are able to restore the ERP elasticsearch index to RM index. With total of 10 indices, and total size of 4.5 gb