This was with the cloud-dev solrcloud-start.sh script (after that I've used solrcloud-start-existing.sh).
Essentially I run ./solrcloud-start-existing.sh index docs kill 1 of the solr instances (using kill -9 on the pid) delete a doc from running instances restart killed solr instance on doing this the deleted document is still lingering in the instance that was down. On Fri, Feb 17, 2012 at 2:04 PM, Mark Miller <markrmil...@gmail.com> wrote: > Hmm...just tried this with only deletes, and the replica sync'd fine for me. > > Is this with your multi core setup or were you trying with instances? > > On Feb 17, 2012, at 1:52 PM, Jamie Johnson wrote: > >> Yes, still seeing that. Master has 8 items, replica has 9. So the >> delete didn't seem to work when the node was down. >> >> On Fri, Feb 17, 2012 at 1:41 PM, Yonik Seeley >> <yo...@lucidimagination.com> wrote: >>> On Fri, Feb 17, 2012 at 1:38 PM, Jamie Johnson <jej2...@gmail.com> wrote: >>>> Something that didn't work though >>>> was if a node was down when a delete happened and then comes back up, >>>> that node still listed the id I deleted. Is this currently supported? >>> >>> Yes, that should work fine. Are you still seing that behavior? >>> >>> -Yonik >>> lucidimagination.com > > - Mark Miller > lucidimagination.com > > > > > > > > > > >
