[
https://issues.apache.org/jira/browse/NIFI-14355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17934493#comment-17934493
]
Pierre Villard commented on NIFI-14355:
---------------------------------------
So after thinking a bit more about this... Given that
* the API rate limit is scoped to the credentials and different sets of
credentials could be used across different NiFi deployments
* it is possible to change the version of a process group to a newer version
even if the process group version icon is not (yet) showing that a new version
is available (you just right click / change version and go to the latest
version)
I think the best immediate solution is to change the value in the code to a
larger number and see if that is enough to help.
If some of our largest users are still facing such rate limit issues, we can
re-evaluate to make this configurable through the NiFi configuration.
I'll file a PR to change the value to 30 minutes. I think this is still
providing a good balance for users that might be in a dev environment and want
to see new versions quickly versus an environment in prod where it does not
really matter that much.
> Authenticated GitHub Registry Client hitting rate limit (5000 reqs per hour)
> ----------------------------------------------------------------------------
>
> Key: NIFI-14355
> URL: https://issues.apache.org/jira/browse/NIFI-14355
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Flow Versioning, NiFi Registry
> Affects Versions: 2.2.0
> Environment: Not relevant
> Reporter: Andrea Di Stefano
> Priority: Major
> Attachments: image-2025-03-11-16-47-39-522.png
>
>
> Hello.
> We are using the GitHub Registry Client with a Personal Authentication Token
> (PAT) and constantly hitting the API rate limit. The rate limit, [as stated
> in the GitHub
> docs|https://docs.github.com/en/rest/using-the-rest-api/rate-limits-for-the-rest-api?apiVersion=2022-11-28#primary-rate-limit-for-authenticated-users],
> is 5000 requests per hour.
> We have a pipeline with 53 instances of 3 versioned process groups, which are
> part of a bigger pipeline (~1.1k components).
> I uploaded a related stack trace [here|https://pastebin.com/R0tTw4bP].
> Calling the GitHub API with Postman, we saw that the response headers include
> data about the rate limit, current usage, and reset time in Unix epoch
> format, see the attached screenshot for an example:
> !image-2025-03-11-16-47-39-522.png!
> Is NiFi periodically polling the GitHub API in background?
> Can we somehow limit the number of calls?
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
