JIRA Health Check Warning

[Drew Bentley]

Why is the latest JIRA Health Check plugin warning about the Thread Limit setting at 4096 and recommends setting it at 4,096? This is like the "keyboard error, press any key to continue" type of error. 

This is silly!

[Niclas Sandstroem]

Drew could you provide a screenshot so we see what you mean? Do you get rid of the warning by increasing the limit?

[Drew Bentley]

So I set my ulimits according to Jira's docs recommended settings. 4096 soft and 8192 hard, I still got the health check warning.

Jira_Health_Check_Stupidity.png

[Niclas Sandstroem]

Weird I don't get any warning on Linux. I have the latest versions of all. What OS you on? If Linux you can compare to my /proc/<PID>/limits .

Limit                     Soft Limit           Hard Limit           Units
Max cpu time              unlimited            unlimited            seconds
Max file size             unlimited            unlimited            bytes
Max data size             unlimited            unlimited            bytes
Max stack size            8388608              unlimited            bytes
Max core file size        0                    unlimited            bytes
Max resident set          unlimited            unlimited            bytes
Max processes             63785                63785                processes
Max open files            4096                 4096                 files
Max locked memory         65536                65536                bytes
Max address space         unlimited            unlimited            bytes
Max file locks            unlimited            unlimited            locks
Max pending signals       63785                63785                signals
Max msgqueue size         819200               819200               bytes
Max nice priority         0                    0
Max realtime priority     0                    0
Max realtime timeout      unlimited            unlimited            us

[Drew Bentley]

Using latest CentOS. This never complained until the most recent healthcheck plugin updates.

So it seems if I set my soft limit to 4097, the error goes away.

$ ulimit -u
4097

$ cat /etc/security/limits.d/20-nproc.conf
# Default limit for number of user's processes to prevent
# accidental fork bombs.
# See rhbz #432903 for reasoning.

* soft nproc 4096
root soft nproc unlimited
jira soft nproc 4097
jira hard nproc 8192

I just find the error odd that it would tell me that my max process setting is 4096 and I should set it to 4,096 in the error message.

[Niclas Sandstroem]

Agreed but its most likely a validation bug. Just report it in their support portal if you want them to address it