On 8/4/23 11:43, Jayesh Shende wrote:
The NRTCachingDirectoryFactory is trying to cache as much segments as
possible into the memory, but the queries are for different collections and
are varying (less of repetitive query terms), so thinking this cached
segments are not actually very useful here,
requests.
I switched to NIOFS reader and disk problem was solved. Just don’t expect Solr
to be super fast as it was with a small index which could fit in RAM.
-ufuk
Sent from Mail for Windows
From: Jayesh Shende
Sent: Friday, August 4, 2023 8:44 PM
To: users@solr.apache.org
Subject: Re: Changing Solr
Hi Shawn,
Thanks for responding so quickly.
The server box is shared by multiple Solr nodes, each node is having more
than 100gb of disk usage (~2-4 replicas of different collections on one
Solr).
The NRTCachingDirectoryFactory is trying to cache as much segments as
possible into the memory, but
On 8/4/23 09:56, Jayesh Shende wrote:
Using: Solr 8.11.2 with rhel9
Currently using "solr.NRTCachingDirectoryFactory" for a collection,
the collection has grown big in size, but don't want to add more RAM to
machine(AWS),
I can increase IOPS and througput for data volume.
Was thinking of using
Hi everyone,
Using: Solr 8.11.2 with rhel9
Currently using "solr.NRTCachingDirectoryFactory" for a collection,
the collection has grown big in size, but don't want to add more RAM to
machine(AWS),
I can increase IOPS and througput for data volume.
Was thinking of using "solr.NIOFSDirectoryFactor
