On 5 September 2016 at 11:02, Ganesh M <ganesh.sudhakar....@gmail.com> wrote: > My big question is why is that SOLR can't throw the error when it's not > able to handle the request due to concurrency or for other reason.
Solr SHOULD throw an error if there is an issue. The problem is that the concurrency is a HARD problem with a lot of moving parts. So far, we can't even figure out in which subsystem you are seeing the unusual behavior to figure out whether it is a misconfiguration, misunderstanding, bug, or something completely different. However, if you are repeating exactly the same test with the same documents multiple times and getting different documents missing in the end, that does sound like a bug. The question is whether it is a known and fixed bug or something completely new. Any chance you could try this against 6.2? Even in test environment/VM, if you cannot put Java 8 anywhere near production. Regards, Alex. ---- Newsletter and resources for Solr beginners and intermediates: http://www.solr-start.com/
