These parameters are commented in my solr config.xml

see the parameters attached.

<!-- The RunExecutableListener executes an external command from a
      hook such as postCommit or postOptimize.
         exe - the name of the executable to run
         dir - dir to use as the current working directory. default="."
         wait - the calling thread waits until the executable returns.
default="true"
         args - the arguments to pass to the program.  default=nothing
         env - environment variables to set.  default=nothing
      -->
    <!-- A postCommit event is fired after every commit or optimize command
    <listener event="postCommit" class="solr.RunExecutableListener">
      <str name="exe">solr/bin/snapshooter</str>
      <str name="dir">.</str>
      <bool name="wait">true</bool>
      <arr name="args"> <str>arg1</str> <str>arg2</str> </arr>
      <arr name="env"> <str>MYVAR=val1</str> </arr>
    </listener>
    -->
    <!-- A postOptimize event is fired only after every optimize command
    <listener event="postOptimize" class="solr.RunExecutableListener">
      <str name="exe">snapshooter</str>
      <str name="dir">solr/bin</str>
      <bool name="wait">true</bool>
    </listener>
    -->


When i do optimize on index of size 400 mb , it reduces the size of data
folder to 200 mb. But when data is huge it doubles it.
Why is that so?

Optimization : Actually should reduce the size of the data ? Or
just improves the search query performance?






On Fri, Dec 16, 2011 at 5:40 PM, Juan Pablo Mora <jua...@informa.es> wrote:

> Maybe you are generating a snapshot of your index attached to the optimize
> ???
> Look for post-commit or post-optimize events in your solr-config.xml
>
> ________________________________________
> De: Rajani Maski [rajinima...@gmail.com]
> Enviado el: viernes, 16 de diciembre de 2011 11:11
> Para: solr-user@lucene.apache.org
> Asunto: Solr Optimization Fail
>
> Hi,
>
>  When we do optimize, it actually reduces the data size right?
>
> I have index of size 6gb(5 million documents). Index is already created
> with commits for every 10000 documents.
>
> Now I was trying to do optimization with  http optimize command.   When i
> did that,  data size became - 12gb.  Why this might have happened?
>
> And can anyone please suggest me fix for it?
>
> Thanks
> Rajani
>

Reply via email to