Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

In a Nifi-workflow some of the processors are not showing start button ?

Solved Go to solution
Highlighted

Re: In a Nifi-workflow some of the processors are not showing start button ?

Expert Contributor

@Veerendra Nath JasthiPossibly, you have a complicated computation (may be regex) running on Getfile, which is taking a lot of time to

complete, also check howmany files it is getting based on your regex, it should be fixed.

Highlighted

Re: In a Nifi-workflow some of the processors are not showing start button ?

Explorer

No I have been using the plain getFile which is having input as a simple folder and we are not doing any regex on those files.

FYI.... In my entire workflow all processors are behaving the same.

Highlighted

Re: In a Nifi-workflow some of the processors are not showing start button ?

Expert Contributor
@Veerendra Nath Jasthi

What is the frequency of files and how big are the files in the given path? Also could you please check your JVM heap memory (this is a guess, not solution)?

Re: In a Nifi-workflow some of the processors are not showing start button ?

Explorer

I've seen the problem you describe with getfile processor when I used it with nifi deployed on Windows OS and the directory I listed had very large number of recursive subdirectories. In source files of nifi 1.3 or 1.4 I noticed there was a code replacing listfiles with DirectoryInputStream methods, but later it was removed

Don't have an account?
Coming from Hortonworks? Activate your account here