On 5/3/2013 9:28 AM, vicky desai wrote:
Hi,
When a auto commit operation is fired I am getting the following logs
INFO: start
commit{,optimize=false,openSearcher=false,waitSearcher=true,expungeDeletes=false,softCommit=false,prepareCommit=false}
setting the openSearcher to false definetly gave m
Hi,
When a auto commit operation is fired I am getting the following logs
INFO: start
commit{,optimize=false,openSearcher=false,waitSearcher=true,expungeDeletes=false,softCommit=false,prepareCommit=false}
setting the openSearcher to false definetly gave me a lot of performance
improvement but wa
Since you have define commit option as "Auto Commit" for hard and soft
commit then you don't have to explicitly call commit from SolrJ client. And
openSearcher=false for hard commit will make hard commit faster since it is
only makes sure that recent changes are flushed to disk (for durability)
an
Hi,
After using the following config
500
1000
5000
false
When a commit operation is fired I am getting the follow
Hi All,
setting opensearcher flag to true solution worked and it give me visible
improvement in commit time. One thing to make note of is that while using
solrj client we have to call server.commit(false,false) which i was doing
incorrectly and hence was not able to see the improvement earliear.
My solrconfig.xml is as follows
LUCENE_40
2147483647
simple
true
500
1000
That's not ideal.
Can you post solrconfig.xml?
On 3 May 2013 07:41, "vicky desai" wrote:
> Hi sandeep,
>
> I made the changes u mentioned and tested again for the same set of docs
> but
> unfortunately the commit time increased.
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3
Hi Gopal,
I added the opensearcher parameter as mentioned by you but on checking logs
I found that apensearcher was still true on commit. it is only when I
removed the autosoftcommit parameter the opensearcher parameter worked and
provided faster updates as well. however I require soft commit in m
Hi sandeep,
I made the changes u mentioned and tested again for the same set of docs but
unfortunately the commit time increased.
--
View this message in context:
http://lucene.472066.n3.nabble.com/commit-in-solr4-takes-a-longer-time-tp4060396p4060622.html
Sent from the Solr - User mailing lis
Hi Vicky,
I faced this issue as well and after some playing around I found the
autowarm count in cache sizes to be a problem.
I changed that from a fixed count (3072) to percentage (10%) and all commit
times were stable then onwards.
HTH,
Sandeep
On 2 May 2013 16:31, Alexandre Rafalovitch
If you don't re-open the searcher, you will not see new changes. So,
if you only have hard commit, you never see those changes (until
restart). But if you also have soft commit enabled, that will re-open
your searcher for you.
Regards,
Alex.
Personal blog: http://blog.outerthoughts.com/
LinkedI
What happens exactly when you don't open searcher at commit?
2013/5/2 Gopal Patwa
> you might want to added openSearcher=false for hard commit, so hard commit
> also act like soft commit
>
>
> 5
> 30
>fal
you might want to added openSearcher=false for hard commit, so hard commit
also act like soft commit
5
30
false
On Thu, May 2, 2013 at 12:16 AM, vicky desai wrote:
> Hi,
>
> I am using 1
First, I would upgrade to 4.2.1 and remember to change to
LUCENE_42.
There were a LOT of fixes between 4.0 and 4.2.1.
wunder
On May 2, 2013, at 12:16 AM, vicky desai wrote:
> Hi,
>
> I am using 1 shard and two replicas. Document size is around 6 lakhs
>
>
> My solrconfig.xml is as follows
Hi,
I am using 1 shard and two replicas. Document size is around 6 lakhs
My solrconfig.xml is as follows
LUCENE_40
2147483647
simple
true
500
Can you explain more about your document size, shard and replica sizes, and
auto/soft commit time parameters?
2013/5/2 vicky desai
> Hi all,
>
> I have recently migrated from solr 3.6 to solr 4.0. The documents in my
> core
> are getting constantly updated and so I fire a code commit after every
16 matches
Mail list logo
