Was able to get around it for now sending the REQUESTRECOVERY command to the replica. Will open an improvement JIRA but not sure if it's worth it as the work-around is pretty clean (IMO).
Tim On Tue, Aug 19, 2014 at 5:33 PM, Mark Miller <markrmil...@gmail.com> wrote: > I’d just file a JIRA. Merge, like optimize and a few other things, were never > tested or considered in early SolrCloud days. It’s used in the HDFS stuff, > but in that case, the index is merged to all replicas and no recovery is > necessary. > > If you want to make the local filesystem merge work well with SolrCloud, > sounds like we should write a test and make it work. > > -- > Mark Miller > about.me/markrmiller > > On August 19, 2014 at 1:20:54 PM, Timothy Potter (thelabd...@gmail.com) wrote: >> Hi, >> >> Using the coreAdmin mergeindexes command to merge an index into a >> leader (SolrCloud mode on 4.9.0) and the replica does not do a snap >> pull from the leader as I would have expected. The merge into the >> leader worked like a charm except I had to send a hard commit after >> that (which makes sense). >> >> I'm guessing the replica would snap pull from the leader if I >> restarted it, but reloading the collection or core does not trigger >> the replica to pull from the leader. This seems like an oversight in >> the mergeindex interaction with SolrCloud. Seems like the simplest >> would be for the leader to send all replicas a request recovery >> command after performing the merge. >> >> Advice? >> >> Cheers, >> Tim >> >
