SolrCloud does need up to twice the amount of disk space as your usual index size during replication. Amongst other things, this ensures you have a full copy of the index at any point. There's no way around this, I would suggest you provision the additional disk space needed. On 20 Apr 2015 23:21, "Rishi Easwaran" <rishi.easwa...@aol.com> wrote:
> Hi All, > > We are seeing this problem with solr 4.6 and solr 4.10.3. > For some reason, solr cloud tries to recover and creates a new index > directory - (ex:index.20150420181214550), while keeping the older index as > is. This creates an issues where the disk space fills up and the shard > never ends up recovering. > Usually this requires a manual intervention of bouncing the instance and > wiping the disk clean to allow for a clean recovery. > > Any ideas on how to prevent solr from creating multiple copies of index > directory. > > Thanks, > Rishi. >
