{"_id":"574d18e9cf99610e00ef7f9b","user":"5636bfbf0441020d0000ea03","version":{"_id":"5633ec007e9e880d00af1a56","project":"5633ebff7e9e880d00af1a53","__v":15,"createdAt":"2015-10-30T22:15:28.105Z","releaseDate":"2015-10-30T22:15:28.105Z","categories":["5633ec007e9e880d00af1a57","5633f072737ea01700ea329d","5637a37d0704070d00f06cf4","5637cf4e7ca5de0d00286aeb","564503082c74cf1900da48b4","564503cb7f1fff210078e70a","567af26cb56bac0d0019d87d","567afeb8802b2b17005ddea0","567aff47802b2b17005ddea1","567b0005802b2b17005ddea3","568adfffcbd4ca0d00aebf7e","56ba80078cf7c9210009673e","574d127f6f075519007da3d0","574fde60aef76a0e00840927","57a22ba6cd51b22d00f623a0"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"category":{"_id":"574d127f6f075519007da3d0","project":"5633ebff7e9e880d00af1a53","__v":0,"version":"5633ec007e9e880d00af1a56","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-05-31T04:26:39.925Z","from_sync":false,"order":3,"slug":"versions","title":"Versions"},"__v":13,"project":"5633ebff7e9e880d00af1a53","parentDoc":null,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-05-31T04:54:01.317Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"examples":{"codes":[]},"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":2,"body":"Navigate to your cluster dashboard and follow our in-depth guide here:\n\n- https://docs.bonsai.io/docs/upgrading-your-version\n[block:callout]\n{\n  \"type\": \"warning\",\n  \"body\": \"Clusters have to be cleared before upgrading or downgrading versions in Bonsai, but that doesn't mean you have to lose your indices. A good solution is using the elasticsearch-dump tool by Taskrabbit, which you can use to export your data before clearing it for upgrades/downgrades, and importing once the version has changed:\\n\\n- https://github.com/taskrabbit/elasticsearch-dump\\n\\nWe'd like to note that no snapshot tool can replace the safeguard of having a good reindexing script and data loss procedures in place. When designing your indices and integration, keep in mind that Lucene indices were meant for speed, and should not be relied on as a primary data store.\",\n  \"title\": \"Version changing with no data loss\"\n}\n[/block]","excerpt":"","slug":"elasticsearch-2x-upgrade","type":"basic","title":"Elasticsearch 2.4 Upgrade"}

Elasticsearch 2.4 Upgrade


Navigate to your cluster dashboard and follow our in-depth guide here: - https://docs.bonsai.io/docs/upgrading-your-version [block:callout] { "type": "warning", "body": "Clusters have to be cleared before upgrading or downgrading versions in Bonsai, but that doesn't mean you have to lose your indices. A good solution is using the elasticsearch-dump tool by Taskrabbit, which you can use to export your data before clearing it for upgrades/downgrades, and importing once the version has changed:\n\n- https://github.com/taskrabbit/elasticsearch-dump\n\nWe'd like to note that no snapshot tool can replace the safeguard of having a good reindexing script and data loss procedures in place. When designing your indices and integration, keep in mind that Lucene indices were meant for speed, and should not be relied on as a primary data store.", "title": "Version changing with no data loss" } [/block]