Automating Index refreshes

Hi,

I've just taken over support of a web application with a elasticsearch back
end. Currently we do intermittent data refreshes by building an es index
on a build server, zipping it up, copying it over to UAT, stopping Tomcat
and elastic search, copying over the new index structure, doing some minor
config (change the top level folder name (in the data folder) from app_dev
to app_uat to app_live) and then restarting the services.

I'm pretty new to this but I'm wondering if anyone has any opinions on the
best way to automate this process ? We would rather continue to rebuild
the index on the build server if possible but I'm guessing there may be a
better way to do a data refresh than to build a convoluted dos script (we
are using a windows environment)

Any suggestions or help much appreciated.

Thanks

Ben.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/b3c005b6-6471-4b2a-ac50-ed072a45b527%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Look into snapshot/restore

http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-snapshots.html

Jörg

On Thu, Oct 2, 2014 at 12:18 PM, gringogordo benkdishman@gmail.com wrote:

Hi,

I've just taken over support of a web application with a elasticsearch
back end. Currently we do intermittent data refreshes by building an es
index on a build server, zipping it up, copying it over to UAT, stopping
Tomcat and elastic search, copying over the new index structure, doing some
minor config (change the top level folder name (in the data folder) from
app_dev to app_uat to app_live) and then restarting the services.

I'm pretty new to this but I'm wondering if anyone has any opinions on the
best way to automate this process ? We would rather continue to rebuild
the index on the build server if possible but I'm guessing there may be a
better way to do a data refresh than to build a convoluted dos script (we
are using a windows environment)

Any suggestions or help much appreciated.

Thanks

Ben.

--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/b3c005b6-6471-4b2a-ac50-ed072a45b527%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/b3c005b6-6471-4b2a-ac50-ed072a45b527%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEgQ%2BWTbythMacJ1UGMRGFY%2B9W0mXXV1sSRW_f_bKodNQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Many thanks for this. I've realised now we are running a fairly old
version (0.90.11) which I don't think has this functionality (?). I guess
I'll push on anyway but out of interest do you think I'll encounter many
issues upgrading from 0.90 to 1.3 ?

Thanks

On Thursday, October 2, 2014 11:38:05 AM UTC+1, Jörg Prante wrote:

Look into snapshot/restore

http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-snapshots.html

Jörg

On Thu, Oct 2, 2014 at 12:18 PM, gringogordo <benkd...@gmail.com
<javascript:>> wrote:

Hi,

I've just taken over support of a web application with a elasticsearch
back end. Currently we do intermittent data refreshes by building an es
index on a build server, zipping it up, copying it over to UAT, stopping
Tomcat and elastic search, copying over the new index structure, doing some
minor config (change the top level folder name (in the data folder) from
app_dev to app_uat to app_live) and then restarting the services.

I'm pretty new to this but I'm wondering if anyone has any opinions on
the best way to automate this process ? We would rather continue to
rebuild the index on the build server if possible but I'm guessing there
may be a better way to do a data refresh than to build a convoluted dos
script (we are using a windows environment)

Any suggestions or help much appreciated.

Thanks

Ben.

--
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 elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/b3c005b6-6471-4b2a-ac50-ed072a45b527%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/b3c005b6-6471-4b2a-ac50-ed072a45b527%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/32ce2897-828a-475a-a187-7d9cc75f971b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.