[
https://issues.apache.org/jira/browse/SOLR-6998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282470#comment-14282470
]
Pawel Rog edited comment on SOLR-6998 at 1/19/15 1:12 PM:
----------------------------------------------------------
I think you shouldn't be worried about Virtual size. Please take a look at
column which shows 1095M. Is it "RES" size? This would mean your heap is only
1G and maybe you send some huge document packages which causes OOM. Please let
know how big is your document pack sent to /update resource.
BTW I see your machine is 8GB RAM. Please remember that you can use bigger heap
(-Xmx parameter for jvm). 4GB seems to be good (half of system memory).
was (Author: prog):
I think you shouldn't be worried about Virtual size. Please take a look at
column which shows 1095M. Is it "RES" size? This would mean your heap is only
1G and maybe you send some huge document packages which causes OOM. Please let
know how big is your document pack sent to /update resource.
> java.lang.OutOfMemoryError: Java heap space
> -------------------------------------------
>
> Key: SOLR-6998
> URL: https://issues.apache.org/jira/browse/SOLR-6998
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.10.2
> Environment: Ubuntu 14.04, RAM=8GB
> Reporter: Alexandru Iacob
> Labels: solr
>
> After deploying SOLR 4.10.2 in a master-slave configuration, I'm getting this
> errors all over the place on the master ...
> From the web-ui -> Logging -> http://i.imgur.com/qFzMlJL.png
> "Caused by: org.apache.lucene.store.AlreadyClosedException: this IndexWriter
> is closed"
> and
> "Caused by: java.lang.OutOfMemoryError: Java heap space".
> I have checked the server and it looklike the VM size is quite big ->
> http://i.imgur.com/MZZZkGD.png
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
