Re: [VuFind-General] [solrmarc-tech] RE: Record import "killed"?

[Simon S. <ses...@gm...>]

On Wed, Mar 14, 2012 at 2:08 PM, Demian Katz <dem...@vi...>wrote:

> There are two ways to solve your problem:
>
> 1.) Get more RAM.  If you are using a physical server, you probably need
> to buy and install some.  If you are using a virtual server, you'll have to
> change some configurations.  The specifics will vary based on your
> circumstances.
>
> 2.) Reduce the amount of RAM Solr expects -- edit vufind.sh and change
> this line:
>
>  JAVA_OPTIONS="-server -Xms1024m -Xmx1024m -XX:+UseParallelGC
> -XX:NewRatio=5"
>
> You can replace the 1024m numbers with something smaller -- maybe 512m or
> 256m.  In the long term, you will probably need more memory than that to
> get good performance unless your index is very small...  but for testing
> purposes, this may be enough to get you to the next step.
>

["Error occurred during initialization of VM : Could not reserve enough
space for object heap"]

There are several possible reasons why it might not be possible to reserve
enough space:

1) There really isn't enough virtual memory available; adding swap space
will allow the process to start.  This may or may not cause thrashing
depending on how much swap space that is already allocated is currently
being used.
You can experiment by adding more swap space in a file on a regular
partition; on linux, see man pages for mkswap(8) and swapon(8).
You can stop using this  swapspace using swapoff; you should then delete
the file (16GB).

2) The amount of virtual memory available per process for the user running
the VM is restricted by a ulimit .
Check for this by running ulimit -a  and looking to see if the setting for
virtual memory is "unlimited".  This must be done as the user who will be
running jetty, and not as root.  If a ulimit is set, only root can increase
it.

3) You may be running a 32 bit JVM or on a 32bit OS.
Switch to 64bit

Simon