Another reason could be insufficient memory available with the OS. I faced a similar issue in the past, after releasing some amount of memory it works. e.g Machine/Server has 6 GB total memory, Java process allocated 5.4 GB and OS left with 600MB, It was causing the same issue(unable to create native thread). After reducing memory allocated to the java and leaving a significant amount of memory for the OS, it works.
Thanks, Rajendra Gaikwad On Thu, Jan 20, 2022 at 9:14 PM Shawn Heisey <apa...@elyograg.org> wrote: > On 1/20/22 5:54 AM, 123456780sss wrote: > > 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? > > To see what the actual effective limits are on Linux for a running > process, you can do the following command, where NNNNN is the pid of the > process you want to check: > > cat /proc/NNNNN/limits > > I do not know what options area available for other operating systems. > > 4096 is probably enough, I just like to allow something higher just in > case it it suddenly needs more to handle a momentary spike in load. I > think the highest thread count I ever saw for a Solr instance when > checking it with jconsole is somewhere in the neighborhood of 1300, on a > large install for the company I was working for at the time. Looking at > the tiny Solr instance I am running for mail server, right now it has 46 > threads. I have the system-wide per-user limits for nproc and nofile > set to 8192, far more than I need. The entire system shows 618 > threads/processes in use, which is a lot less than I expected to see. > > Thanks, > Shawn > > >
