gt;
>
>
>
> Can you help me why Iam getting this error.
>
> PFA of the same error log and the solr-spring.xml files.
>
> Regards,
> Lokanadham Ganta
>
> ----- Original Message -
> From: "Erick Erickson [via Lucene]" <
> ml-node+s472066n4101220.
kanadham Ganta
- Original Message -
From: "Erick Erickson [via Lucene]"
To: "Loka"
Sent: Friday, November 15, 2013 7:14:26 PM
Subject: Re: exceeded limit of maxWarmingSearchers ERROR
That's a fine place to start. This form:
${solr.autoCommit.maxTime:15000}
j
:15000}
>false
>
>
>
>
>
>${solr.autoSoftCommit.maxTime:1}
>
>
>
>
> Please confirm me.
>
> But how can I check how much autowarming that Iam doing, as of now I have
> set the maxWarmingSearchers as 2, should
false
Is the above one fine?
Regards,
Lokanadham Ganta
- Original Message -
From: "Lokanadham Ganta"
To: "Erick Erickson [via Lucene]"
Sent: Friday, November 15, 2013 6:33:20 PM
Subject: Re: exceeded limit of maxWarmingSearchers ERROR
Erickson,
T
- Original Message -
From: "Erick Erickson [via Lucene]"
To: "Loka"
Sent: Friday, November 15, 2013 6:07:12 PM
Subject: Re: exceeded limit of maxWarmingSearchers ERROR
Where did you get that syntax? I've never seen that before.
What you want to configure is the "ma
ing wrong.
>
> Regards,
> Lokanadham Ganta
>
>
>
>
>
>
>
>
>
>
> ----- Original Message -
> From: "Erick Erickson [via Lucene]" <
> ml-node+s472066n4100924...@n3.nabble.com>
> To: "Loka"
> Sent: Thursday, November 14, 2013
Erick Erickson [via Lucene]"
To: "Loka"
Sent: Thursday, November 14, 2013 8:38:17 PM
Subject: Re: exceeded limit of maxWarmingSearchers ERROR
CommitWithin is either configured in solrconfig.xml for the
or tags as the maxTime tag. I
recommend you do use this.
The other way you ca
CommitWithin is either configured in solrconfig.xml for the
or tags as the maxTime tag. I
recommend you do use this.
The other way you can do it is if you're using SolrJ, one of the
forms of the server.add() method takes a number of milliseconds
to force a commit.
You really, really do NOT want
Hi Naveen,
Iam also getting the similar problem where I do not know how to use the
commitWithin Tag, can you help me how to use commitWithin Tag. can you give
me the example
--
View this message in context:
http://lucene.472066.n3.nabble.com/exceeded-limit-of-maxWarmingSearchers-ERROR-tp3252844
Hi Nagendra,
Thanks a lot .. i will start working on NRT today.. meanwhile old settings
(increased warmSearcher in Master) have not given me trouble till now ..
but NRT will be more suitable to us ... Will work on that one and will
analyze the performance and share with you.
Thanks
Naveen
2011/
Naveen:
See below:
*NRT with Apache Solr 3.3 and RankingAlgorithm does need a commit for a
document to become searchable*. Any document that you add through update
becomes immediately searchable. So no need to commit from within your
update client code. Since there is no commit, the cache does
Nagendra
You wrote,
Naveen:
*NRT with Apache Solr 3.3 and RankingAlgorithm does need a commit for a
document to become searchable*. Any document that you add through update
becomes immediately searchable. So no need to commit from within your
update client code. Since there is no commit, the c
Bill:
I did look at Marks performance tests. Looks very interesting.
Here is the Apacle Solr 3.3 with RankingAlgorithm NRT performance:
http://solr-ra.tgels.com/wiki/en/Near_Real_Time_Search_ver_3.x
Regards
- Nagendra Nagarajayya
http://solr-ra.tgels.org
http://rankingalgorithm.tgels.org
On
I understand.
Have you looked at Mark's patch? From his performance tests, it looks
pretty good.
When would RA work better?
Bill
On 8/14/11 8:40 PM, "Nagendra Nagarajayya"
wrote:
>Bill:
>
>The technical details of the NRT implementation in Apache Solr with
>RankingAlgorithm (SOLR-RA) is avai
Bill:
The technical details of the NRT implementation in Apache Solr with
RankingAlgorithm (SOLR-RA) is available here:
http://solr-ra.tgels.com/papers/NRT_Solr_RankingAlgorithm.pdf
(Some changes for Solr 3.x, but for most it is as above)
Regarding support for 4.0 trunk, should happen someti
OK,
I'll ask the elephant in the roomÂ.
What is the difference between the new UpdateHandler from Mark and the
SOLR-RA?
The UpdateHandler works with 4.0 does SOLR-RA work with 4.0 trunk?
Pros/Cons?
On 8/14/11 8:10 PM, "Nagendra Nagarajayya"
wrote:
>Naveen:
>
>NRT with Apache Solr 3.3 and Ra
Naveen:
NRT with Apache Solr 3.3 and RankingAlgorithm does need a commit for a
document to become searchable. Any document that you add through update
becomes immediately searchable. So no need to commit from within your
update client code. Since there is no commit, the cache does not have
It's worth noting that the fast commit rate is only an indirect part
of the issue you're seeing. As the error comes from cache warming - a
consequence of committing, it's not the fault of commiting directly.
It's well worth having a good close look at exactly what you're caches
are doing when they
It's somewhat confusing - I'll straighten it out though. I left the issue open
to keep me from taking forever to doc it - hasn't helped much yet - but maybe
later today...
On Aug 14, 2011, at 12:12 PM, Erick Erickson wrote:
> Ah, thanks, Mark... I must have been looking at the wrong JIRAs.
>
>
Hi Mark/Erick/Nagendra,
I was not very confident about NRT at that point of time, when we started
project almost 1 year ago, definitely i would try NRT and see the
performance.
The current requirement was working fine till we were using commitWithin 10
millisecs in the XMLDocument which we were p
Ah, thanks, Mark... I must have been looking at the wrong JIRAs.
Erick
On Sun, Aug 14, 2011 at 10:02 AM, Mark Miller wrote:
>
> On Aug 14, 2011, at 9:03 AM, Erick Erickson wrote:
>
>> You either have to go to near real time (NRT), which is under
>> development, but not committed to trunk yet
>
>
Naveen:
You should try NRT with Apache Solr 3.3 and RankingAlgorithm. You can
update 10,000 documents / sec while also concurrently searching. You can
set commit freq to about 15 mins or as desired. The 10,000 document
update performance is with the MBArtists index on a dual core Linux
syste
On Aug 14, 2011, at 9:03 AM, Erick Erickson wrote:
> You either have to go to near real time (NRT), which is under
> development, but not committed to trunk yet
NRT support is committed to trunk.
- Mark Miller
lucidimagination.com
You either have to go to near real time (NRT), which is under
development, but not committed to trunk yet or just stop
warming up searchers and let the first user to open a searcher
pay the penalty for warmup, (useColdSearchers as I remember).
Although I'd also ask whether this is a reasonable req
24 matches
Mail list logo
