Sorry - yes, I meant to say leader. Each JVM has 16G of memory.
On 10 April 2014 20:54, Erick Erickson <erickerick...@gmail.com> wrote: > First, there is no "master" node, just leaders and replicas. But that's a > nit. > > No real clue why you would be going out of memory. Deleting a > document, even by query should just mark the docs as deleted, a pretty > low-cost operation. > > how much memory are you giving the JVM? > > Best, > Erick > > On Thu, Apr 10, 2014 at 6:25 PM, Vinay Pothnis <poth...@gmail.com> wrote: > > [solr version 4.3.1] > > > > Hello, > > > > I have a solr cloud (4 nodes - 2 shards) with a fairly large amount > > documents (~360G of index per shard). Now, a major portion of the data is > > not required and I need to delete those documents. I would need to delete > > around 75% of the data. > > > > One of the solutions could be to drop the index completely re-index. But > > this is not an option at the moment. > > > > When we tried to delete the data through a query - say 1 day/month's > worth > > of data. But after deleting just 1 month's worth of data, the master node > > is going out of memory - heap space. > > > > Wondering is there any way to incrementally delete the data without > > affecting the cluster adversely. > > > > Thank! > > Vinay >
