nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James McMahon <>
Subject Avoiding Forced Refreshes that Result in Lost Changes
Date Wed, 12 Apr 2017 17:03:19 GMT
We have multiple people working is separate distinct processor groups under
a common NiFi instance. As would be expected, they are often making changes
to their processor group workflows concurrently.

There are long periods of time where Betty loses any attempted changes
including reposition of processors, configuration changes, etc because
Timmy has made changes in his processor group. The system prompts Betty
with a synchronization alert message, and when she then closes that pop up
alert her changes are gone. The message posted to Betty in such
circumstances is:

"This NiFi instance has been updated by 'SMITH TIMMY. Please refresh to
synchronize the view."

Two related questions:
1. why are the changes in a Processor Group impacting the other when there
are no dependencies other than the services each may use?
2. Is it possible to avoid this with a configuration change?
3. does Timmy have to be fired because he keeps getting in Betty's way?

-Jim (yes, Timmy)

View raw message