Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-14475

Rate Limiting Connection to Github Enterprise

XMLWordPrintable

    • 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.

      When the DVCS Connector communicates with github.com, it is (I think) able to understand and respect rate limit headers.

      Unfortunately, Github Enterprise disables rate limiting, so it's possible for the DVCS Connector to swamp a GHE instance with many, many requests. We have measured periods in which we received 600 requests/second between our JIRA host and our Github Enterprise instance.

      Based on a support issue, we've set jira.devstatus.applink.ratelimit to 60, but we anecdotally observe that it seems to affect the rate on a per-organization basis. If there are pushes to multiple repositories in several different organizations at about the same time, the request rates will spike again.

      We would like to be able to specify that our JIRA host should never exceed N requests per second to our Github Enterprise instance for any reason.

            [JSWSERVER-14475] Rate Limiting Connection to Github Enterprise

            David Marshall added a comment -

            Thank you for the update. I understand your reasoning for deferring work on this. I don't know that it's necessary for JIRA (or any such system) to manage its behavior this way, because it's something that the other system to take care of. For instance, Github Enterprise ought to use the same rate-limiting headers as github.com does, or organizations such as ours should install some sort of rate-limiting intermediary.

            I would recommend adding some information about this to the JIRA Knowledge Base, however! As it turns out, we've lowered jira.devstatus.applink.ratelimit even further, to 10.

            David Marshall added a comment - Thank you for the update. I understand your reasoning for deferring work on this. I don't know that it's necessary for JIRA (or any such system) to manage its behavior this way, because it's something that the other system to take care of. For instance, Github Enterprise ought to use the same rate-limiting headers as github.com does, or organizations such as ours should install some sort of rate-limiting intermediary. I would recommend adding some information about this to the JIRA Knowledge Base, however! As it turns out, we've lowered jira.devstatus.applink.ratelimit even further, to 10.

            Benjamin Morgan (Inactive) added a comment -

            Thanks dmarshal we appreciate that this is a problem for you and we will tag this for assessment in future projects.

            While this is something we want to take care of, looking at our current priorities we will not be addressing this in the immediate future.

            Benjamin Morgan (Inactive) added a comment - Thanks dmarshal we appreciate that this is a problem for you and we will tag this for assessment in future projects. While this is something we want to take care of, looking at our current priorities we will not be addressing this in the immediate future.

              Unassigned Unassigned
              44f150fdeece David Marshall
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: