There is no usable stack trace: : Error creating bean with name 'neoService': Invocation of init method failed; nested exception is java.lang.OutOfMemoryError: Requested array size exceeds VM limit
Further testing indicates that it is either the node_cache_array_fraction and the relationship_cache_array_faction are causing the problem. It is supposed to default to 1%. On an 150G heap that should be 1.5G. However the array size being generated is too long. Explicitly setting node_cache_size and relationship_cache_size seems to address this although it is far from ideal. Clark Richey [email protected] > On May 6, 2015, at 8:24 PM, Sumit Gupta <[email protected]> wrote: > > hi, > > Please provide the exact exception along with the modified parameters. > > Thanks, > Sumit > > On Wednesday, 6 May 2015 20:21:51 UTC+5:30, Clark Richey wrote: > Hello, > I’m running Neo4J 2.2.1 with 150G heap space on a box with 240G. I set the > neo4j.neostore.nodestore.dbms.pagecache.memory > to 60G (slightly less than 75% of remaining system memory as recommended). > However, when I startup I get an error that the system can’t start because > I’m trying to allocate an array whose size exceeds the maximum allowed size. > > > > --- > Clark Richey > [email protected] <javascript:> > > > > > -- > You received this message because you are subscribed to the Google Groups > "Neo4j" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
