Does this happen on a fresh Solr 6.3 ( as mentioned on SOLR-10806 ) or was the index existing with some other version and then upgraded to 6.3 ?
Is the problem reproducible for you? On Tue, Jun 6, 2017 at 7:26 AM, S G <sg.online.em...@gmail.com> wrote: > Hi, > > We are seeing some very bad performance on our performance test that tries > to load a 2 shard, 3 replica system with about 2000 writes/sec and 2000 > reads/sec > > The exception stack trace seems to point to a specific line of code and a > similar stack trace is reported by users on Elastic-Search forums too. > > Could this be a a common bug in Lucene which is affecting both the systems? > https://issues.apache.org/jira/browse/SOLR-10806 > > One bad part about Solr is that once it happens, the whole system comes to > a grinding halt. > Solr UI is not accessible, even for the nodes not hosting any collections ! > It would be really nice to get rid of such an instability in the system. > > Thanks > SG > > >