-
Suggestion
-
Resolution: Won't Do
-
None
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Quite a few customers run into the problem in Loss of Functionality due to Too Many Open Files Error, where their instance stops working because the max file limit has been reached. We could workaround this by adding a ulimit set to $JIRA_INSTALL/bin/setenv.sh, for example:
ulimit -n 4096
This would serve to prevent customers from running into this problem without requiring larger non-trivial coding changes as in JRA-33887. Can you please add changes to setenv.sh to set this argument? Thanks
- is related to
-
JRASERVER-33463 Increase the ulimit by default for JIRA installation
- Closed
- relates to
-
JRACLOUD-33887 Implement JIRA Lucene Index NFS Support
- Closed
[JRACLOUD-33463] Increase the ulimit by default for JIRA installation
Workflow | Original: JAC Suggestion Workflow [ 3155593 ] | New: JAC Suggestion Workflow 3 [ 3641185 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2330666 ] | New: JAC Suggestion Workflow [ 3155593 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2096787 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2330666 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2060742 ] | New: JIRA Bug Workflow w Kanban v6 [ 2096787 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 1835833 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2060742 ] |
Description |
Original:
Quite a few customers run into the problem in [Loss of Functionality due to Too Many Open Files Error|https://confluence.atlassian.com/display/JIRAKB/Loss+of+Functionality+due+to+Too+Many+Open+Files+Error], where their instance stops working because the max file limit has been reached. We could workaround this by adding a ulimit set to {{$JIRA_INSTALL/bin/setenv.sh}}, for example: {code} ulimit -n 4096 {code} This would serve to prevent customers from running into this problem without requiring larger non-trivial coding changes as in JRA-33887. Can you please add changes to {{setenv.sh}} to set this argument? Thanks :) |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRASERVER-33463]. {panel} Quite a few customers run into the problem in [Loss of Functionality due to Too Many Open Files Error|https://confluence.atlassian.com/display/JIRAKB/Loss+of+Functionality+due+to+Too+Many+Open+Files+Error], where their instance stops working because the max file limit has been reached. We could workaround this by adding a ulimit set to {{$JIRA_INSTALL/bin/setenv.sh}}, for example: {code} ulimit -n 4096 {code} This would serve to prevent customers from running into this problem without requiring larger non-trivial coding changes as in JRA-33887. Can you please add changes to {{setenv.sh}} to set this argument? Thanks :) |
Link |
New:
This issue is related to |
Project Import | New: Sat Apr 01 19:36:47 UTC 2017 [ 1491075407146 ] |