# Storing Elasticsearch configuraton and deploying new clusters **URL:** \ **Category:** Elasticsearch\ **Created:** [August 5, 2014, 9:43pm UTC](https://discuss.elastic.co/t/storing-elasticsearch-configuraton-and-deploying-new-clusters/19105 "2014-08-05T21:43:46Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Hayden\_Muhl](https://avatars.discourse-cdn.com/v4/letter/h/47e85d/32.png) [@Hayden\_Muhl](https://discuss.elastic.co/u/Hayden_Muhl)\ **Post date:** [August 5, 2014, 9:43pm UTC](https://discuss.elastic.co/t/storing-elasticsearch-configuraton-and-deploying-new-clusters/19105/1 "2014-08-05T21:43:46Z")
We've been using Solr for the past several months, but have been considering Elasticsearch recently. One think I can't quite wrap my head around is how to keep track of Elasticsearch cluster configuration. Solr is largely based on config files written in XML. These are very straight forward to handle. You store them in your repository, and when deploying a new system, you drop the config files in the right places and start up Solr. Elasticsearch configuration all seems to happen via the API. If I set up a cluster for QA, and get it configured the way I want, how would I then go about deploying a production environment with the same configuration? What processes do people here use for deploying new environments? -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/54240e8e-3e91-43c8-9275-343c49333b0f%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/54240e8e-3e91-43c8-9275-343c49333b0f%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [August 5, 2014, 11:45pm UTC](https://discuss.elastic.co/t/storing-elasticsearch-configuraton-and-deploying-new-clusters/19105/2 "2014-08-05T23:45:58Z")
There are some settings you can set via the API, but not all. The docs are pretty indepth so check out > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 6 August 2014 07:43, Hayden Muhl [haydenmuhl@gmail.com](mailto:haydenmuhl@gmail.com) wrote: > We've been using Solr for the past several months, but have been > considering Elasticsearch recently. > > One think I can't quite wrap my head around is how to keep track of > Elasticsearch cluster configuration. Solr is largely based on config files > written in XML. These are very straight forward to handle. You store them > in your repository, and when deploying a new system, you drop the config > files in the right places and start up Solr. > > Elasticsearch configuration all seems to happen via the API. If I set up a > cluster for QA, and get it configured the way I want, how would I then go > about deploying a production environment with the same configuration? What > processes do people here use for deploying new environments? > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/54240e8e-3e91-43c8-9275-343c49333b0f%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/54240e8e-3e91-43c8-9275-343c49333b0f%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/54240e8e-3e91-43c8-9275-343c49333b0f%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/54240e8e-3e91-43c8-9275-343c49333b0f%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624Zj%3DdgB%3DKBL5D6wpwxzzUGHHHDdmEOzoo3WeenQY1jngw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624Zj%3DdgB%3DKBL5D6wpwxzzUGHHHDdmEOzoo3WeenQY1jngw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Hayden\_Muhl](https://avatars.discourse-cdn.com/v4/letter/h/47e85d/32.png) [@Hayden\_Muhl](https://discuss.elastic.co/u/Hayden_Muhl)\ **Post date:** [August 6, 2014, 12:03am UTC](https://discuss.elastic.co/t/storing-elasticsearch-configuraton-and-deploying-new-clusters/19105/3 "2014-08-06T00:03:22Z")
I was thinking more in terms of things like mappings. The only way of setting up mappings that I can find is via the API. If I've set up and tested a particular way of indexing and querying my documents on a QA system, I want to set my production system up the same way. What is your process for doing this? On Tue, Aug 5, 2014 at 4:45 PM, Mark Walkom [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) wrote: > There are some settings you can set via the API, but not all. > The docs are pretty indepth so check out > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-configuration.html) > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > On 6 August 2014 07:43, Hayden Muhl [haydenmuhl@gmail.com](mailto:haydenmuhl@gmail.com) wrote: > > > We've been using Solr for the past several months, but have been > > considering Elasticsearch recently. > > > > One think I can't quite wrap my head around is how to keep track of > > Elasticsearch cluster configuration. Solr is largely based on config files > > written in XML. These are very straight forward to handle. You store them > > in your repository, and when deploying a new system, you drop the config > > files in the right places and start up Solr. > > > > Elasticsearch configuration all seems to happen via the API. If I set up > > a cluster for QA, and get it configured the way I want, how would I then go > > about deploying a production environment with the same configuration? What > > processes do people here use for deploying new environments? > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/54240e8e-3e91-43c8-9275-343c49333b0f%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/54240e8e-3e91-43c8-9275-343c49333b0f%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/54240e8e-3e91-43c8-9275-343c49333b0f%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/54240e8e-3e91-43c8-9275-343c49333b0f%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/RDbwZSPSII0/unsubscribe](https://groups.google.com/d/topic/elasticsearch/RDbwZSPSII0/unsubscribe). > To unsubscribe from this group and all its topics, send an email to > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAEM624Zj%3DdgB%3DKBL5D6wpwxzzUGHHHDdmEOzoo3WeenQY1jngw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624Zj%3DdgB%3DKBL5D6wpwxzzUGHHHDdmEOzoo3WeenQY1jngw%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAEM624Zj%3DdgB%3DKBL5D6wpwxzzUGHHHDdmEOzoo3WeenQY1jngw%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEM624Zj%3DdgB%3DKBL5D6wpwxzzUGHHHDdmEOzoo3WeenQY1jngw%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAGqgWec\_r\_o%3De9RQq3Hjk6sUcdv2%2BA\_NoM%2BDPr5jTbJMg1tmSw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAGqgWec_r_o%3De9RQq3Hjk6sUcdv2%2BA_NoM%2BDPr5jTbJMg1tmSw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [August 6, 2014, 12:07am UTC](https://discuss.elastic.co/t/storing-elasticsearch-configuraton-and-deploying-new-clusters/19105/4 "2014-08-06T00:07:49Z")
You can store mappings on the filesystem - > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 6 August 2014 10:03, Hayden Muhl [haydenmuhl@gmail.com](mailto:haydenmuhl@gmail.com) wrote: > I was thinking more in terms of things like mappings. The only way of > setting up mappings that I can find is via the API. If I've set up and > tested a particular way of indexing and querying my documents on a QA > system, I want to set my production system up the same way. What is your > process for doing this? > > On Tue, Aug 5, 2014 at 4:45 PM, Mark Walkom [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) > wrote: > > > There are some settings you can set via the API, but not all. > > The docs are pretty indepth so check out > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-configuration.html) > > > > Regards, > > Mark Walkom > > > > Infrastructure Engineer > > Campaign Monitor > > email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) > > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > > > On 6 August 2014 07:43, Hayden Muhl [haydenmuhl@gmail.com](mailto:haydenmuhl@gmail.com) wrote: > > > > > We've been using Solr for the past several months, but have been > > > considering Elasticsearch recently. > > > > > > One think I can't quite wrap my head around is how to keep track of > > > Elasticsearch cluster configuration. Solr is largely based on config files > > > written in XML. These are very straight forward to handle. You store them > > > in your repository, and when deploying a new system, you drop the config > > > files in the right places and start up Solr. > > > > > > Elasticsearch configuration all seems to happen via the API. If I set up > > > a cluster for QA, and get it configured the way I want, how would I then go > > > about deploying a production environment with the same configuration? What > > > processes do people here use for deploying new environments? > > > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "elasticsearch" group. > > > To unsubscribe from this group and stop receiving emails from it, send > > > an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/54240e8e-3e91-43c8-9275-343c49333b0f%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/54240e8e-3e91-43c8-9275-343c49333b0f%40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/54240e8e-3e91-43c8-9275-343c49333b0f%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/54240e8e-3e91-43c8-9275-343c49333b0f%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > -- > > You received this message because you are subscribed to a topic in the > > Google Groups "elasticsearch" group. > > To unsubscribe from this topic, visit > > [https://groups.google.com/d/topic/elasticsearch/RDbwZSPSII0/unsubscribe](https://groups.google.com/d/topic/elasticsearch/RDbwZSPSII0/unsubscribe). > > To unsubscribe from this group and all its topics, send an email to > > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/CAEM624Zj%3DdgB%3DKBL5D6wpwxzzUGHHHDdmEOzoo3WeenQY1jngw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624Zj%3DdgB%3DKBL5D6wpwxzzUGHHHDdmEOzoo3WeenQY1jngw%40mail.gmail.com) > > [https://groups.google.com/d/msgid/elasticsearch/CAEM624Zj%3DdgB%3DKBL5D6wpwxzzUGHHHDdmEOzoo3WeenQY1jngw%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEM624Zj%3DdgB%3DKBL5D6wpwxzzUGHHHDdmEOzoo3WeenQY1jngw%40mail.gmail.com?utm_medium=email&utm_source=footer) > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAGqgWec\_r\_o%3De9RQq3Hjk6sUcdv2%2BA\_NoM%2BDPr5jTbJMg1tmSw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAGqgWec_r_o%3De9RQq3Hjk6sUcdv2%2BA_NoM%2BDPr5jTbJMg1tmSw%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAGqgWec\_r\_o%3De9RQq3Hjk6sUcdv2%2BA\_NoM%2BDPr5jTbJMg1tmSw%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAGqgWec_r_o%3De9RQq3Hjk6sUcdv2%2BA_NoM%2BDPr5jTbJMg1tmSw%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624avLLZSqNp6U22q4h-FyrCuc9s%2Bamx1N-8do71jvGhqUA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624avLLZSqNp6U22q4h-FyrCuc9s%2Bamx1N-8do71jvGhqUA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [August 6, 2014, 6:07am UTC](https://discuss.elastic.co/t/storing-elasticsearch-configuraton-and-deploying-new-clusters/19105/5 "2014-08-06T06:07:18Z")
I would prefer having a script file which do everything you need than storing mappings in config/ I find scripts more flexible. You can create index with specific settings, add mapping, inject some data... My 2 cents. -- David 😉 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 5 août 2014 à 23:43, Hayden Muhl [haydenmuhl@gmail.com](mailto:haydenmuhl@gmail.com) a écrit : We've been using Solr for the past several months, but have been considering Elasticsearch recently. One think I can't quite wrap my head around is how to keep track of Elasticsearch cluster configuration. Solr is largely based on config files written in XML. These are very straight forward to handle. You store them in your repository, and when deploying a new system, you drop the config files in the right places and start up Solr. ## Elasticsearch configuration all seems to happen via the API. If I set up a cluster for QA, and get it configured the way I want, how would I then go about deploying a production environment with the same configuration? What processes do people here use for deploying new environments? You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/54240e8e-3e91-43c8-9275-343c49333b0f%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/54240e8e-3e91-43c8-9275-343c49333b0f%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/8DED0EB4-0BCB-4EFE-984D-AFCD54C648BA%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/8DED0EB4-0BCB-4EFE-984D-AFCD54C648BA%40pilato.fr). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:10am UTC](https://discuss.elastic.co/t/storing-elasticsearch-configuraton-and-deploying-new-clusters/19105/6 "2017-07-06T01:10:37Z")