ramBufferSize is preferred to be 128MB more than that it does not seemes to
improve performance
--
View this message in context:
http://lucene.472066.n3.nabble.com/OutOfMemoryErrors-tp1181731p1199592.html
Sent from the Solr - User mailing list archive at Nabble.com.
Yeah fine..I will do that...Before the merge Factor was 10 itself ...After
finding this error I just set its value higher assuming if that could be
error anyway... Will re change it..
The ramBufferSize is 256MB... Do I need to change this value to higher?
On Wed, Aug 18, 2010 at 12:27 AM, Jay
A merge factor of 100 is very high and out of the norm. Try starting with a
value of 10. I've never seen a running system with a value anywhere near
this high.
Also, what is your setting for ramBufferSizeMB?
-Jay
On Tue, Aug 17, 2010 at 10:46 AM, rajini maski wrote:
> yeah sorry I forgot to men
yeah sorry I forgot to mention others...
100
1000
10
1
above are the values
Is this because of values here...initially I had mergeFactor parameter -10
and maxMergedocs-1With the same error i changed them to above
values..Yet I got that error after index was about 2lacs docs..
There are more merge paramaters, what values do you have for these:
10
1000
2147483647
1
See: http://wiki.apache.org/solr/SolrConfigXml
Hope that formatting comes through the various mail programs OK
Also, what else happens while you're indexing? Do you search
while indexing? How often
100
JVM Initial memory pool -256MB
Maximum memory pool -1024MB
long:ID
str:Body
12 fields
I have a solr instance in solr folder (D:/Solr) free space in disc is 24.3GB
.. How will I get to know what portion of memory is solr using ?
On Tue, Aug 17, 2010 at 10:11 PM, Erick E
You shouldn't be getting this error at all unless you're doing something
out of the ordinary. So, it'd help if you told us:
>What parameters you have set for merging
>What parameters you have set for the JVM
>What kind of documents are you indexing?
The memory you have is irrelevant if you only a
Which method do you use to index? If you are using SolrJ you can use the
streaming update server
it is a better option for the solr server, because the server does not
need to held it all in memory.
(if you are using the post.jar file there was bug which causes OOMs but
I didn't remember exactly .
I am getting it while indexing data to solr not while querying...
Though I have enough memory space upto 40GB and I my indexing data is just
5-6 GB yet that particular error is seldom observed... (SEVERE ERROR : JAVA
HEAP SPACE , OUT OF MEMORY ERROR )
I could see one lock file generated in the data
> Is there a way to verify that I have added correctlly?
>
on linux you can do
ps -elf | grep Boot
and see if the java command has the parameters added.
@all: why and when do you get those OOMs? while querying? which queries
in detail?
Regards,
Peter.
U can add like this it will work I am using it
JAVA_OPTS="$JAVA_OPTS -Xms1024m -Xmx4096m "
--
View this message in context:
http://lucene.472066.n3.nabble.com/OutOfMemoryErrors-tp1181731p1183229.html
Sent from the Solr - User mailing list archive at Nabble.com.
Xms256m -Xmx1024m";
>
> On Tue, Aug 17, 2010 at 1:36 PM, Grijesh.singh wrote:
>
>>
>> put that line in your startup script or u can set as env var
>> export CATALINA_OPTS=-Xms256m -Xmx1024m;
>> --
>> View this message in context:
>> http://lucene.472
an set as env var
> export CATALINA_OPTS=-Xms256m -Xmx1024m;
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/OutOfMemoryErrors-tp1181731p1182708.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
--
Chhorn Chamnap
http://chamnapchhorn.blogspot.com/
put that line in your startup script or u can set as env var
export CATALINA_OPTS=-Xms256m -Xmx1024m;
--
View this message in context:
http://lucene.472066.n3.nabble.com/OutOfMemoryErrors-tp1181731p1182708.html
Sent from the Solr - User mailing list archive at Nabble.com.
U can set up in startup script of tomcat
--
View this message in context:
http://lucene.472066.n3.nabble.com/OutOfMemoryErrors-tp1181731p1182582.html
Sent from the Solr - User mailing list archive at Nabble.com.
in same frequency
:(
On Tue, Aug 17, 2010 at 10:42 AM, Grijesh.singh wrote:
>
> increase your JVM Heap space by using params
> -Xms1024m
> -Xmx4096m
>
> Like this.
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/OutOfMemoryErrors-tp1181731p1
increase your JVM Heap space by using params
-Xms1024m
-Xmx4096m
Like this.
--
View this message in context:
http://lucene.472066.n3.nabble.com/OutOfMemoryErrors-tp1181731p1181892.html
Sent from the Solr - User mailing list archive at Nabble.com.
I got this error, anyone could explain and solve this?
SEVERE: Exception invoking periodic operation:
java.lang.OutOfMemoryError: Java heap space
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:114)
at
org.apache.catalina.core.ContainerBase.bac
Hi, I just thought I'd note that upgrading to the 1.4 nightlies solved
my problem.
kind regards,
Tarjei
On 06/17/2009 02:38 PM, tarjei wrote:
Hi, I'm having memory problems on one of my Solr slaves:
SEVERE: Error during auto-warming of
key:org.apache.solr.search.queryresult...@563c7832:java.lan
Hi, I'm having memory problems on one of my Solr slaves:
SEVERE: Error during auto-warming of
key:org.apache.solr.search.queryresult...@563c7832:java.lang.OutOfMemoryError:
Java heap space errors
Jun 17, 2009 1:52:53 PM org.apache.solr.common.SolrException log
SEVERE: Error in xpath:java.lan
20 matches
Mail list logo
