{"_id":"574d1f1ccf99610e00ef7fa4","__v":6,"project":"5633ebff7e9e880d00af1a53","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"},"parentDoc":null,"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"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-05-31T05:20:28.335Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"examples":{"codes":[]},"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":3,"body":"So now you've upgraded your shiny new cluster to Elasticsearch 2.x, and want to downgrade to 1.7.5? If your region [supports Elasticsearch 1.7.5](doc:supported-elasticsearch-versions) for your plan type, you can downgrade.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Downgrading Elasticsearch 2.x Clusters to Elasticsearch 1.7.5\"\n}\n[/block]\nIf you are in a region that uses [Elasticsearch 2.x by default](doc:supported-elasticsearch-versions) but also still supports Elasticsearch 1.7.5, you'll need to clear your cluster of data and then contact [our support](mailto:support:::at:::bonsai.io) and let us know your cluster name so we can downgrade you.\n\nIf you are in a region that uses Elasticsearch 1.7.5 by default, you can follow the same procedure as above, or as a self-service option you can deprovision your cluster and then create a new one in the region. The new cluster will default to Elasticsearch 1.7.5 .\n\nThese are our current recommendations, and we hope to further streamline this process in the future.\n[block:callout]\n{\n  \"type\": \"warning\",\n  \"title\": \"Version changing with no data loss\",\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, not primary data stores.\"\n}\n[/block]","excerpt":"","slug":"elasticsearch-175-downgrade","type":"basic","title":"Elasticsearch 1.7.5 Downgrade"}

Elasticsearch 1.7.5 Downgrade


So now you've upgraded your shiny new cluster to Elasticsearch 2.x, and want to downgrade to 1.7.5? If your region [supports Elasticsearch 1.7.5](doc:supported-elasticsearch-versions) for your plan type, you can downgrade. [block:api-header] { "type": "basic", "title": "Downgrading Elasticsearch 2.x Clusters to Elasticsearch 1.7.5" } [/block] If you are in a region that uses [Elasticsearch 2.x by default](doc:supported-elasticsearch-versions) but also still supports Elasticsearch 1.7.5, you'll need to clear your cluster of data and then contact [our support](mailto:support@bonsai.io) and let us know your cluster name so we can downgrade you. If you are in a region that uses Elasticsearch 1.7.5 by default, you can follow the same procedure as above, or as a self-service option you can deprovision your cluster and then create a new one in the region. The new cluster will default to Elasticsearch 1.7.5 . These are our current recommendations, and we hope to further streamline this process in the future. [block:callout] { "type": "warning", "title": "Version changing with no data loss", "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, not primary data stores." } [/block]