given the fact that you are actually building a new index from scratch, my
shot in the dark didn't hit any target.
When you say : "Once the import finishes we save the docker image in the
AWS docker repository. We then build our cluster using that image as the
Do you mean just configuraiton wise ?
Will the new cluster have any starting index on disk?
If i understood correctly your latest statements I expect a NO in here.
So you are building a completely new index and comparing to the old index (
which is completely separate) you denote such a big difference in size.
This is extremely suspicious .
Optimizing in the end is just a huge merge to force 1 ( or N) final
Given the additional information you gave me, it's not going to make much
I would recommend to check how the index space is divided in different file
( i.e. list how much space is dedicated to a specific extension)
Stored content is in the .fdt files.
Search Consultant, R&D Software Engineer, Director
Sease Ltd. - www.sease.io
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html