Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-33463

Increase the ulimit by default for JIRA installation

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      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

          Form Name

            [JRACLOUD-33463] Increase the ulimit by default for JIRA installation

            Kerrod Williams (Inactive) added a comment -

            Thanks for taking the time to raise this issue.

            Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts. In part, that means concentrating on those issues that resonate the most with our users.

            I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue.

            Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me.

            Kind Regards,
            Kerrod Williams
            JIRA Product Management
            kerrod.williams at atlassian dot com

            Kerrod Williams (Inactive) added a comment - Thanks for taking the time to raise this issue. Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts . In part, that means concentrating on those issues that resonate the most with our users. I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue. Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me. Kind Regards, Kerrod Williams JIRA Product Management kerrod.williams at atlassian dot com

            Tyler Mace added a comment -

            Why is this marked for JIRA only? I believe this behavior is also a problem with Confluence and Bamboo.

            Tyler Mace added a comment - Why is this marked for JIRA only? I believe this behavior is also a problem with Confluence and Bamboo.

            Radek Antoniuk added a comment -

            Regardless of the method, a simple warning in setenv.sh can be implemented if the value is set to default (1024) just as a precaution for the admin starting up JIRA.

            Radek Antoniuk added a comment - Regardless of the method, a simple warning in setenv.sh can be implemented if the value is set to default (1024) just as a precaution for the admin starting up JIRA.

            Sergey Svishchev added a comment -

            This will only work if hard limit is set high enough, otherwise a SA has to raise this limit for the application account.

            Sergey Svishchev added a comment - This will only work if hard limit is set high enough, otherwise a SA has to raise this limit for the application account.

              Unassigned Unassigned
              dcurrie@atlassian.com Dave C
              Votes:
              8 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: