Hi
Thanks for suggestion.
I do following changes in solrconfig.xml :
<ramBufferSizeMB>256</ramBufferSizeMB>
<useColdSearcher>false</useColdSearcher>
<maxWarmingSearchers>1</maxWarmingSearchers>
<autoCommit>
<maxDocs>2000</maxDocs>
<maxTime>300000</maxTime>
</autoCommit>
<lockType>simple</lockType>
<documentCache
class="solr.LRUCache"
size="512"
initialSize="512"
autowarmCount="0"/>
<filterCache
class="solr.FastLRUCache"
size="512"
initialSize="512"
autowarmCount="0"/>
<queryResultCache
class="solr.LRUCache"
size="512"
initialSize="512"
autowarmCount="0"/>
after that, i see one server works fine (that includes 3 cores for 3 languages)
but another server (3 cores for 3 other languages) has problem after 52 hours.
I will plan to do your suggestion. i hope it helps me
any better idea would be appreciated
Kind Regards
Hamid
________________________________
From: Peter Karich <peat...@yahoo.de>
To: solr-user@lucene.apache.org
Sent: Tue, December 7, 2010 8:26:01 PM
Subject: Re: Solr & JVM performance issue after 2 days
Am 07.12.2010 13:01, schrieb Hamid Vahedi:
> Hi Peter
>
> Thanks a lot for reply. Actually I need real time indexing and query at the
>same
> time.
>
> Here told:
> "You can run multiple Solr instances in separate JVMs, with both having
their
> solr.xml configured to use the same index folder."
>
> Now
> Q1: I'm using Tomcat now, Could you please tell me how to have separate JVMs
> with Tomcat?
Are you sure you don't want two servers and you really want real time?
Slow down indexing + less cache should do the trick I think.
I wouldn't recommend indexing AND querying on the same machine unless
you have a lot RAM and CPU.
you could even deploy two indices into one tomcat... the read only index
refers to the data dir via:
<dataDir>/path/to/index/data</dataDir>
then issue an empty (!!) commit to the read only index every minute. so
that the read only index sees the changes from the feeding index.
(again: see the wikipage!)
setting up two tomcats on one server I woudn't recommend too, but its
possible via copying tomcat into, say tomcat2
and change the shutdown and 8080 port in the tomcat2/conf/server.xml
> Q2:What should I set for LockType?
I'm using simple, but native should also be ok.
> Thanks in advanced
>
>
>
>
> ________________________________
> From: Peter Karich<peat...@yahoo.de>
> To: solr-user@lucene.apache.org
> Sent: Tue, December 7, 2010 2:06:49 PM
> Subject: Re: Solr& JVM performance issue after 2 days
>
> Hi Hamid,
>
> try to avoid autowarming when indexing (see solrconfig.xml:
> caches->autowarm + newSearcher + maxSearcher).
> If you need to query and indexing at the same time,
> then probably you'll need one read-only core and one for writing with no
> autowarming configured.
> See: http://wiki.apache.org/solr/NearRealtimeSearchTuning
>
> Or replicate from the indexing-core to a different core with different
> settings.
>
> Regards,
> Peter.
>
>
>> Hi,
>>
>> I am using multi-core tomcat on 2 servers. 3 language per server.
>>
>> I am adding documents to solr up to 200 doc/sec. when updating process is
>> started, every thing is fine (update performance is max 200 ms/doc. with
about
>> 800 MB memory used with minimal cpu usage).
>>
>> After 15-17 hours it's became so slow (more that 900 sec for update), used
>> heap
>> memory is about 15GB, GC time is became more than one hour.
>>
>>
>> I don't know what's wrong with it? Can anyone describe me what's the problem?
>> Is that came from Solr or JVM?
>>
>> Note: when i stop updating, CPU busy within 15-20 min. and when start
updating
>> again i have same issue. but when stop tomcat service and start it again, all
>> thing is OK.
>>
>> I am using tomcat 6 with 18 GB memory on windows 2008 server x64. Solr 1.4.1
>>
>> thanks in advanced
>> Hamid
>
--
http://jetwick.com twitter search prototype
