Nifi parameter provider with constant invalid revision

[#1]

Hey all,

We recently upgrade to nifi 2.4.0 from 1.x and have noticed something weird about the parameter provider in 2.x. From time to time, for some reason, the parameter provider will complain about invalid revision given when fetching for parameters with nifi-cli. Specifically we are using AzureKeyvaultParameterProvider. And the only way to get rid of it is the re-creation of the parameter provider.

See the screenshot 

And it looks like the revision manager was messed up that every time the new revision is always one version below, we are running nifi in a standalone mode and consecutively triggering of the parameter fetch will constantly get the invalid revision(each time the revision is up by 1) until the parameter provider is recreated, even restarting nifi won't help. I'm also quite sure there is only one person sending request to fetch for parameter and attempt to change the parameter provider at the same time so no concurrent operation. 

And once this problem happens, fetching parameters from UI also does not work, it would just fail silently and the value of the secrets remains unchanged.

Also FYI, this never happened in 1.x

Anyone with similar problem?

[#2]

Looks like a revision tracking issue introduced in NiFi 2.x, especially with how it handles state in the AzureKeyvaultParameterProvider. Since it worked fine in 1.x, it’s likely a regression or a behavior change in how revisions are managed. Until a fix, try logging this with the NiFi Jira or reverting to 1.x if critical.

[#3]

I will try to open a ticket [NIFI-14599] Parameter provider invalid revision issue - ASF JIRA