One more key observation.. it actually appears that the processors are running, even though their icons show that they are stopped. For example, the tasks/time keeps going up even though a GetSQS processor looks stopped. However, the fact that they appear stopped also seems to be confusing the UI, which prevents me from starting any processors that happen to have a thread running.
On Fri, May 12, 2017 at 4:08 PM, Joe Gresock <[email protected]> wrote: > I upgraded a nifi 1.1.1 cluster to 1.2.0, and I'm now finding that all > processors are stopped on startup. However, the flow.xml.gz on disk > appears to have the correct scheduledState values. I'm afraid to touch the > flow in the UI, lest it save all 500 of my processors as stopped. > > Is there anything new in 1.2.0 that would cause this? > > -- > I know what it is to be in need, and I know what it is to have plenty. I > have learned the secret of being content in any and every situation, > whether well fed or hungry, whether living in plenty or in want. I can > do all this through him who gives me strength. *-Philippians 4:12-13* > -- I know what it is to be in need, and I know what it is to have plenty. I have learned the secret of being content in any and every situation, whether well fed or hungry, whether living in plenty or in want. I can do all this through him who gives me strength. *-Philippians 4:12-13*
