Thanks for the tip. Although we have increased our application's heap to 4g and it is still not enough.
I guess here are the things we think we did wrong: - Each SP call will return 15 result sets. - Each document can contain 300-1000 child documents. - If the batch size is 1000, the child documents for each can contain 300-1000 documents so that will eat up the 4g's allocated to the application. Granted if these are the things we did wrong, what strategies can anyone suggest so that our indexing will not fail if the child documents will grow unexpectedly? Should this even happen (main documents containing a ton of child documents)? -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
