On Tue, Jun 14, 2011 at 12:56 PM, Johan Svensson
<jo...@neotechnology.com> wrote:
> Hi,
>
> Looks like there was an OOME during commit but commit partially
> succeeded (removing the xid branch id association for the xa resource)
> causing the subsequent rollback call to fail. To guarantee consistency
> the kernel will block all mutating operations after this and a restart
> + recovery has to be performed.
>
> To avoid this make sure you don't get OOME thrown. What cache
> configuration was this on? If running on strong reference cache
> (default is soft) that may be the cause. Another possible cause is
> that the transaction is to large so either increase heap or split
> large transactions into smaller ones.
This is the configurations I touch during EmbeddedGraphDatabase creation time:
Map<String, String> config = new HashMap<String, String>();
config.put("string_block_size", "60");
config.put("dump_configuration", "true");
config.put("neostore.propertystore.db.index.keys.mapped_memory", "5M");
config.put("neostore.propertystore.db.index.mapped_memory", "5M");
config.put("neostore.propertystore.db.mapped_memory", "350M");
config.put("neostore.propertystore.db.strings.mapped_memory", "100M");
config.put("neostore.relationshipstore.db.mapped_memory", "350M");
I got 2G of heap space but I may increase a little and the transaction
consists at max of 10000 "insert" operations.
One characteristic of my db is to have a single node indexed with
millions of values, let's say I have one node has the target of one
index which contains one indexed property with 250millions of
values... may this cause problems?
Cheers
--
Massimo
http://meridio.blogspot.com
_______________________________________________
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
