Tools for moving and saving indicies.
(local)
npm install elasticdump ./bin/elasticdump(global)
npm install elasticdump -g elasticdumpelasticdump works by sending an input to an output. Both can be either an elasticsearch URL or a File.
Elasticsearch:
- format:
{protocol}://{host}:{port}/{index} - example:
http://127.0.0.1:9200/my_index
File:
- format:
{FilePath} - example:
/Users/evantahler/Desktop/dump.json
Stdio:
- format: stdin / stdout
- format: $
You can then do things like:
# Copy an index from production to staging: elasticdump --input=http://production.es.com:9200/my_index --output=http://staging.es.com:9200/my_index # Backup an index to a file: elasticdump --input=http://production.es.com:9200/my_index --output=/data/my_index.json # Backup and index to a gzip using stdout: elasticdump --input=http://production.es.com:9200/my_index --output=$ | gzip > /data/my_index.json.gz # Backup ALL indices, then use Bulk API to populate another ES cluster: elasticdump --all=true --input=http://production-a.es.com:9200/ --output=/data/production.json elasticdump --bulk=true --input=/data/production.json --output=http://production-b.es.com:9200/--input(required) (see above)--output(required) (see above)--limithow many ojbects to move in bulk per operation (default: 100)--debugdisplay the elasticsearch commands being used (default: false)--deletedelete documents one-by-one from the input as they are moved (default: false)--allload/store documents from ALL indices (default: false)--bulkleverage elasticsearch Bulk API when writing documents (default: false)--ignore-errorswill continue the read/write loop on write error (default: false)--scrollTimeTime the nodes will hold the requested search in order. (default: 10m)
Elasticsearch provides a scan and scroll method to fetch all documents of an index. This method is much safer to use since it will maintain the result set in cache for the given period of time. This means it will be a lot faster to export the data and more important it will keep the result set in order. While dumping the result set in batches it won't export duplicate documents in the export. All documents in the export will unique and therefore no missing documents.
NOTE: only works for output
- elasticdump (and elasticsearch in general) will create indices if they don't exist upon import
- we are using the
putmethod to write objects. This means new objects will be created and old objects with the same ID will be updated - the
filetransport will overwrite any existing files - If you need basic http auth, you can use it like this:
--input=http://name:password@production.es.com:9200/my_index - if you choose a stdio output (
--output=$), you can also request a more human-readable output with--format=human - if you choose a stdio output (
--output=$), all logging output will be suppressed
Inspired by https://github.com/crate/elasticsearch-inout-plugin and https://github.com/jprante/elasticsearch-knapsack
Built at TaskRabbit


