Thanks for the advice, it looks like a promising direction. However, we've checked the nproc and nofile in our cluster and right now they are set to 4096 each, unlike the 1024 that was theorized. We will probably try to raise it to 8192 anyway, but we're not sure that the impact will be as great as expected initially. Do you think it's still going to solve the issue?
The amount of threads that we encounter whenever the issue arises is significantly smaller than the nproc (1000 vs 4096), do you think that is an indicator that the origin of the problem is different? Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, January 13th, 2022 at 5:41 PM, Shawn Heisey <apa...@elyograg.org> wrote: > On 1/13/22 8:24 AM, Shawn Heisey wrote: > > > You need to allow the user that is running Solr to have more > > > > processes/threads and more open files. On Linux you can add lines > > > > like the following to /etc/security/limits.conf:| > > > > solr hard nofile 8192|| > > > > solr soft nofile 8192|| > > > > solr hard nproc 8192|| > > > > solr soft nproc 8192| > > I do not know where the | character came from. I did not see it in the > > message that I sent. It should not be there. > > Thanks, > > Shawn
