,
Michael
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-timeout-after-reboot-tp4096408p4100254.html
Sent from the Solr - User mailing list archive at Nabble.com.
Have you considered just putting some killer queries in the firstSearcher
and newSearcher
sections of solrconfig.xml? By "killer" I mean even single queries that
search something
on all the fields you care about, facet on a bunch of fields and sort by a
bunch of
fields. These can even be all in the
Hi Michael,
I agree with Shawn, don't listen to Peter ;) but only this once -
he's a smart guy, as you can see in list archives.
And I disagree with Shawn. again, only just this once and only
somewhat. :) Because:
In general, Shawn's advice is correct, but we have no way of knowing
your
On 10/21/2013 8:03 AM, michael.boom wrote:
> I'm using the m3.xlarge server with 15G RAM, but my index size is over 100G,
> so I guess putting running the above command would bite all available
> memory.
With a 100GB index, I would want a minimum server memory size of 64GB,
and I would much prefer
but my index size is over 100G,
> so I guess putting running the above command would bite all available
> memory.
>
>
>
> -
> Thanks,
> Michael
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Solr-timeout-after-reboot-tp4096408p4096827.html
> Sent from the Solr - User mailing list archive at Nabble.com.
I'm using the m3.xlarge server with 15G RAM, but my index size is over 100G,
so I guess putting running the above command would bite all available
memory.
-
Thanks,
Michael
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-timeout-after-reboot-tp4096408p4096827
Thanks,
> > Michael
> > --
> > View this message in context:
> http://lucene.472066.n3.nabble.com/Solr-timeout-after-reboot-tp4096408p4096809.html
> > Sent from the Solr - User mailing list archive at Nabble.com.
>
>
s message in context:
> http://lucene.472066.n3.nabble.com/Solr-timeout-after-reboot-tp4096408p4096809.html
> Sent from the Solr - User mailing list archive at Nabble.com.
Hmm, no, I haven't...
What would be the effect of this ?
-
Thanks,
Michael
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-timeout-after-reboot-tp4096408p4096809.html
Sent from the Solr - User mailing list archive at Nabble.com.
initialSize="1000"
>autowarmCount="0"/>
>
>
> size="1000"
> initialSize="1000"
> autowarmCount="0" />
>
>
> true
>
> 20
>
>10
1024
true
20
100
active:true
false
10
-
Thanks,
Michael
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-timeout-after-reboot-tp4096408p4096780.html
Sent from the Solr - User mailing li
t can serve?
>
>
>
> -
> Thanks,
> Michael
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Solr-timeout-after-reboot-tp4096408.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
Solr is not warmed up.
What settings could I tweak so that Solr doesn't time out anymore when
getting many requests? Is there a way to limit how many req it can serve?
-
Thanks,
Michael
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-timeout-after-reboot-tp40
mance Monitoring SaaS for Solr -
http://sematext.com/spm/solr-performance-monitoring/index.html
- Original Message -
> From: Jose Aguilar
> To: "solr-user@lucene.apache.org"
> Cc:
> Sent: Wednesday, January 18, 2012 5:50 PM
> Subject: Enforce overall Solr timeou
Hi all,
Is there a setting to enforce an overall timeout for Solr? For example, we are
using setting timeallowed=2000 in solrconfig.xml (using version 3.5), but as
far as I can tell, that only applies to the search part that returns partial
results if it takes more than 2 seconds and returns pa
ts other Cores < 100.000
>
> - Solr1 for Search-Requests - commit every Minute - 5GB Xmx
> - Solr2 for Update-Request - delta every Minute - 4GB Xmx
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/getting-much-double-Values-from-solr-timeout-tp2650981p26
for Search-Requests - commit every Minute - 5GB Xmx
- Solr2 for Update-Request - delta every Minute - 4GB Xmx
--
View this message in context:
http://lucene.472066.n3.nabble.com/getting-much-double-Values-from-solr-timeout-tp2650981p2654725.html
Sent from the Solr - User mailing list archive
-
View this message in context:
http://lucene.472066.n3.nabble.com/getting-much-double-Values-from-solr-timeout-tp2650981p2654721.html
Sent from the Solr - User mailing list archive at Nabble.com.
B Xmx
> - Solr2 for Update-Request - delta every 2 Minutes - 4GB Xmx
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/getting-much-double-Values-from-solr-timeout-tp2650981p2650981.html
> Sent from the Solr - User mailing list archive at Nabble.com.
ing-much-double-Values-from-solr-timeout-tp2650981p2650981.html
Sent from the Solr - User mailing list archive at Nabble.com.
Every time you reload the index it is to rebuild the facet cached
data. Could that be it?
Also, how big are the fields being highlighted? And are they indexed
with term vectors? (If not, the text is re-analyzed in flight with
term vectors.)
How big are the caches? Are they growing & growing?
On
I use the following article as a reference when dealing with GC related issues
http://www.petefreitag.com/articles/gctuning/
I suggest you activate the verbose option and send GC stats to a file. I don't
remember exactly what
was the option but you should find the information easily
Good luck
>Have you looked at the garbage collector statistics? I've experienced this
>kind of issues in the past
and I was getting huge spikes when the GC was doing its job.
I haven't, and I'm not sure what a good way to monitor this is. The
problem occurs maybe once a week on a server. Should I run jstat
Have you looked at the garbage collector statistics? I've experienced this kind
of issues in the past
and I was getting huge spikes when the GC was doing its job.
On 2010-06-09, at 10:52 AM, Paul wrote:
> Hi all,
>
> In my app, it seems like solr has become slower over time. The index
> has gro
Hi all,
In my app, it seems like solr has become slower over time. The index
has grown a bit, and there are probably a few more people using the
site, but the changes are not drastic.
I notice that when a solr search is made, the amount of cpu and ram
spike precipitously.
I notice in the solr lo
If you have a number of long queries running, your system can become CPU
bound resulting in low throughput and high response times. There are
many ways you can construct a query that will cause it to take a long
time to process, but the SOLR-502 patch can only address the ones where
the work i
Hello All,
Prior to SOLR 1.3 and nutch patch integration - what actually is the effect of
SOLR (non)-timeout? Do the threads eventally die? DOes a new request cause a
new query thread to open, or is the system locked?
What causes a timeout- a complex query?
Is SOLR 1.2 open to DoS attack
27 matches
Mail list logo