Not so much resolved as worked around.  We had a large number of components on the canvas.  And we think we tracked the issue to timeouts in the cluster sync process.  (It was taking too long sometimes to get flow.xml sync'd between the nodes so it would stop.) The default timeout is 30 seconds.  We moved it up to 180 seconds. In Cloudera Manager, for the NiFi Configuration, search for properties which start with `nifi.cluster` to find the ones we changed. I also think things might have gotten better with more recent releases.  We have not seen this happen for quite some time. ... View more

@kellerj, Has the reply helped resolve your issue? If so, can you please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future?  If you are still experiencing the issue, can you provide the information @TimothySpann  has requested? ... View more

Yep!  Had moved on to that after your response and written up a JIRA for my team to build the needed tool.  Thanks again for the response.  My plan is the below   > Find all the processors which may have state, then check if each has state, and if so, clear it.   Find processors of used types which can contain state: e.g., QueryDatabaseTableRecord For each, pull the state by the ID and check if it has any stored state if totalEntryCount of cluster or local state is non-zero If so, call the clear state endpoint Query URL: /nifi-api/flow/search-results?q=QueryDatabaseTableRecord Pull Processor State: /nifi-api/processors/41584e33-adc6-171d-0000-0000581caccb/state Clear Processor State: POST /nifi-api/processors/41584e33-adc6-171d-0000-0000581caccb/state/clear-requests   ... View more

Sure.  I had to make some extract it from a larger PG and make some adjustments due to key code being in a parameter.  But the remainder of the parameters are really placeholders for your environment information.  The main complication might be that I used a few external controller services that you will have to replace.  But their names in the externalControllerServices JSON should help you replace them.   ... View more

Disappointing, but what I was starting to suspect after going through CM's console.  Is there general guidance on including those types of files to the NiFi nodes? ... View more

Thank you!  I looked, but not in the right place.  I skimmed over the bucket API, but didn't look in detail as I assumed (incorrectly) that it was not relevant to updating a flow. ... View more

Thank you so much!  I was looking around for the way to add arbitrary properties to the nifi-registry.properties and never hit on the right wording to find that one.  Yep, figured I could always add the file manually if I could just do what you showed how to. ... View more

I did end up finding a hacky way to do this.  But something using APIs or the registry would be preferred.  It was a multi-step process:   Bring up a new NiFi server. Import the process group from the JSON file into the canvas. Stop the server and copy out flow.xml.gz Rebuild the server to get an empty flow.xml.gz, then stop it again. Unzip and edit both files. Copy the contents of the only <processorGroup> tag to replace the contents of the <rootGroup> Update the coordinates in the new root group to 0.0/0.0. Copy the <parameterContexts> over <parameterContexts/> in the new file. re-zip the updated file and start up the server. Re-enable broken controller services. Not pretty, but it worked to restore a server from a JSON export copy I had made with minimal fixes in NiFi itself.  If there is no easier way, I hope this helps someone else. ... View more