Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-33463

Increase the ulimit by default for JIRA installation

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? 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

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

            Micah B. made changes -
            Remote Link Original: This issue links to "Page (Atlassian Documentation)" [ 117231 ]
            Sarah A made changes -
            Remote Link Original: This issue links to "Page (Atlassian Documentation)" [ 128758 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3047737 ] New: JAC Suggestion Workflow 3 [ 3673363 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2606959 ] New: JAC Suggestion Workflow [ 3047737 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2558891 ] New: Confluence Workflow - Public Facing v4 [ 2606959 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2344302 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2558891 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2117269 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2344302 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2077468 ] New: JIRA Bug Workflow w Kanban v6 [ 2117269 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 882792 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2077468 ]
            jonah (Inactive) made changes -
            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 Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-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 :)

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

                Created:
                Updated:
                Resolved: