Hi all, This issue is still surfacing in the new Soir 8.0.0. Can't really figure out what is the issue, as it occurs also in system with more memory.
Anyone has any further insights on this? Regards, Edwin On Fri, 15 Feb 2019 at 18:40, Zheng Lin Edwin Yeo <edwinye...@gmail.com> wrote: > Hi Shawn, > > This issue is also occurring in the new Solr 7.7.0, with only the same > data size of 20 GB. > > Regards, > Edwin > > On Fri, 8 Feb 2019 at 23:53, Zheng Lin Edwin Yeo <edwinye...@gmail.com> > wrote: > >> Hi Shawn, >> >> Thanks for your reply. >> >> Although the space in the OS disk cache could be the issue, but we didn't >> face this problem previously, especially in our other setup using Solr >> 6.5.1, which contains much more data (more than 1 TB), as compared to our >> current setup in Solr 7.6.0, in which the data size is only 20 GB. >> >> Regards, >> Edwin >> >> >> >> On Wed, 6 Feb 2019 at 23:52, Shawn Heisey <apa...@elyograg.org> wrote: >> >>> On 2/6/2019 7:58 AM, Zheng Lin Edwin Yeo wrote: >>> > Hi everyone, >>> > >>> > Does anyone has further updates on this issue? >>> >>> It is my strong belief that all the software running on this server >>> OTHER than Solr is competing with Solr for space in the OS disk cache, >>> and that Solr's data is getting pushed out of that cache. >>> >>> Best guess is that with only one collection, the disk cache was able to >>> hold onto Solr's data better, and that with another collection present, >>> there's not enough disk cache space available to cache both of them >>> effectively. >>> >>> I think you're going to need a dedicated machine for Solr, so Solr isn't >>> competing for system resources. >>> >>> Thanks, >>> Shawn >>> >>
