Re: few and huge tlogs

2013-09-17 Thread Erick Erickson
Probably because you're indexing a lot of documents
very quickly. It's entirely reasonable to have
much shorter autoCommit times, all that does is
1> truncate the transaction log
2> close the current segment
3> start a new segment.

That should cut down your tlog files drastically. Try
setting your autocommit time to, say, 15000 (15 seconds).

Long blog here:
http://searchhub.org/2013/08/23/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/

Best,
Erick


On Tue, Sep 17, 2013 at 5:16 AM, YouPeng Yang wrote:

> Hi
>   According to
> http://wiki.apache.org/solr/SolrPerformanceProblems#Slow_startup。
>   It explains that the tlog file will swith to a new when hard commit
> happened.
>
>
>   However,my tlog shows different.
> tlog.003   5.16GB
> tlog.004   1.56GB
> tlog.002   610.MB
>
>   there are only a fewer tlogs which suppose to be ten files, and each one
> is vary huge.Even there are lots of hard commit happened.
>
>  So why the number of the tlog files does not increase ?
>
>
>   here are settings of the  DirectUpdateHandler2:
>  
>
>   
>   ${solr.ulog.dir:}
>
>
>   
>120
>100
>false
>  
>
>
>   
>  60
>50
>
>
> 
>


few and huge tlogs

2013-09-17 Thread YouPeng Yang
Hi
  According to
http://wiki.apache.org/solr/SolrPerformanceProblems#Slow_startup。
  It explains that the tlog file will swith to a new when hard commit
happened.


  However,my tlog shows different.
tlog.003   5.16GB
tlog.004   1.56GB
tlog.002   610.MB

  there are only a fewer tlogs which suppose to be ten files, and each one
is vary huge.Even there are lots of hard commit happened.

 So why the number of the tlog files does not increase ?


  here are settings of the  DirectUpdateHandler2:
 

  
  ${solr.ulog.dir:}
   

  
   120
   100
   false
 


  
 60
   50