We recently upgraded to Nifi version 1.17.0 and now our nifi-app.log is filled with the following WARN level log [Validate Components Thread-5] org.apache.avro.LogicalTypes Ignoring invalid logical type for name: timestamp-millis And this just keeps going every couple of seconds. We have not made any changes re the "Use Avro Logical Types" option in ExecuteSQL processes, they are all using default false. What do we need to do to stop this warning from flooding the log file?
... View more
There has been this Nifi issue since late June, about a month after the client had upgraded their Nifi version from 1.12.1 to 1.16.0. The process is essentially a lot of Windows file handling. Checking if a file exists, moving it to different folders, unzipping files, then sorting files by a certain prefix into SQL called store procedures. This process that begins at midnight daily is supposed to be completed by 7am, but the client complaint was that many files were beginning to go over this deadline, only completing much later. Analysing the available data shows that the number of files being processed per hour dropped from about 3000 in version 1.12.1 to about 2000 in 1.16.0. The client ruled out Nifi version upgrade as a cause because that was about a month before they brought up the complaint. However we recently upgraded again from 1.16.0 to 1.17.0 and suddenly the issue has been resolved. But we have yet to identify what the issue causing the file process bottlenecking was. Among some solutions attempted prior to upgrading the version were to increase concurrent thread count of some processes from 5 to 10 threads, and to set both min and max of the JVM heap to 16GB, but none of which worked. Any suggestion on what we can further explore is much appreciated.
... View more