Index creation and deployment strategies

(gringogordo) #1

I have inherited a nice little java app which uses an elasticSearch Index as a back end data source.

At the moment the index is built from scratch every week on a build server and then the service is stopped (on UAT then Live) and the old cluster replaced by the new one.

I am rewriting the app the recreate the index and for various reasons we need to keep doing a full rebuild to replace the existing one each week but I'm thinking there must be a better way than this fairly manual approach ?

Is there a standard approach for this kind of deployment or do people normally live in a world where they are updating / deleting / adding on existing indexes ?

(David Pilato) #2

You should look at aliases.
I think this could help a lot to do that without any interruption.

(system) #3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.