Hello! Do you have some backup after commit in your configuration? It would also be good to see how your index directory looks like, can you list that ?
-- Regards, Rafał Kuć Sematext :: http://sematext.com/ :: Solr - Lucene - ElasticSearch > Thanks Rafal for reply... > I agree with you. But Actually After optimization , it does not reduce size > and it remains double. so is there any thing we missed or need to do for > achieving index size reduction ? > Is there any special setting we need to configure for replication? > On 13 June 2013 16:53, Rafał Kuć <r....@solr.pl> wrote: >> Hello! >> >> Optimize command needs to rewrite the segments, so while it is >> still working you may see the index size to be doubled. However after >> it is finished the index size will be usually lowered comparing to the >> index size before optimize. >> >> -- >> Regards, >> Rafał Kuć >> Sematext :: http://sematext.com/ :: Solr - Lucene - ElasticSearch >> >> > Hi, >> > I have solr server 1.4.1 with index file size 428GB.Now When I upgrade >> solr >> > Server 1.4.1 to Solr 3.5.0 by replication method. Size remains same. >> > But when optimize index for Solr 3.5.0 instance its size reaches 791GB.so >> > what is solutions for size remains same or lesser. >> > I optimize Solr 3.5 with Query: >> > <solr3.5 url>/update?optimize=true&commit=true >> >> > Thanks & regards >> > Viresh Modi >> >>
