I was wrong in saying that we don't need to open a searcher, we do. I committed a fix in SOLR-5314 to use soft commits instead of hard commits. I also increased the read time out value. Both of these together will reduce the likelyhood of such a thing happening.
https://issues.apache.org/jira/browse/SOLR-5314 On Tue, Oct 8, 2013 at 1:24 PM, Shalin Shekhar Mangar < shalinman...@gmail.com> wrote: > Hi Kalle, > > The problem here is that certain actions are taking too long causing the > split process to terminate in between. For example, a commit on the parent > shard leader took 83 seconds in your case but the read timeout value is set > to 60 seconds only. We actually do not need to open a searcher during this > commit. I'll open an issue and attach a fix. > > Longer term we need to introduce asynchronous commands so that status can > be reported in a better way. > > > On Tue, Oct 8, 2013 at 12:13 PM, Kalle Aaltonen < > kalle.aalto...@zemanta.com> wrote: > >> >> I have a test system where I have a index of 15M documents in one shard >> that I would like to split in two. I've tried it four times now. I have a >> stand-alone zookeeper running on the same machine. >> >> The end result is that I have two new shards with state "construction", >> and each has one replica which is down. >> >> Two of the attempts failed because of heapspace. Now the heap size is >> 24GB. I can't figure out from the logs what is going on. >> >> I've attached a log of the latest attempt. Any help would be much >> appreciated. >> >> - Kalle Aaltonen >> >> >> >> > > > -- > Regards, > Shalin Shekhar Mangar. > -- Regards, Shalin Shekhar Mangar.
