Community Articles

Find and share helpful community-sourced technical articles.
Announcements
Celebrating as our community reaches 100,000 members! Thank you!
Labels (1)
avatar
Expert Contributor

When NiFi flow runs in mission critical production environment, customer would concern about how to change NiFi flow logic but don't impact business.

One solution was implemented in customer production is as follow steps:

1. Add an extra non-logic processor, for example "UpdateAttribute", between ListenPort and main ProcessGroup

13515-screen-shot-2017-03-10-at-231459.png

2. Updated NewProcessGroup, add into canvas

13514-screen-shot-2017-03-10-at-235618.png

3. Stop "UpdateAttribute" process, make sure RunningProcessGroup consume all flowfiles in the previous queue. But client components can still send messages to Listen Port

13516-screen-shot-2017-03-10-at-232620.png

4. After all queued flowfiles are processed by RunningProcessGroup, move the queue end connection to the NewProcessGroup

13517-screen-shot-2017-03-10-at-232713.png

5. Start "UPdateAttribute" process and NewProcessGroup

13518-screen-shot-2017-03-10-at-232759.png

6. At the end, remove the old RunningProcessGroup

13519-screen-shot-2017-03-10-at-232914.png

Follow these steps, the production flow change is transparent for client components, and guarantee no data lost.


screen-shot-2017-03-10-at-232620.png
734 Views
0 Kudos
Version history
Last update:
‎08-17-2019 01:51 PM
Updated by:
Expert Contributor Expert Contributor
Contributors