Over a million developers have joined DZone.

Finding NiFi Errors

DZone's Guide to

Finding NiFi Errors

Not sure how to find NiFi errors (especially the odd ones)? Learn how to hunt it down so you can move on with your task or project.

· Big Data Zone
Free Resource

Effortlessly power IoT, predictive analytics, and machine learning applications with an elastic, resilient data infrastructure. Learn how with Mesosphere DC/OS.

I have a Phoenix PutSQL that worked in the past, but not today. The error box was not much help either. I thought maybe Hbase or Phoenix was done, but it turned out that one field was missing. Now, how should I investigate this issue?

Image title

Digging through the logs I quickly found it:

Caused by: java.sql.SQLException: ERROR 218 (23018): Constraint violation. DRONEDATA1.DATEKEY may not be null

That would be nice in the error listed in NiFi. (If something seems like an odd error, dig into the logs for more detailed descriptions. Also, the Summary Screen is pretty awesome and will let you find a lot of information for debugging and fixing problems.)

The Connections tab will let you sort by Queue Size and you can see if things are backed up.

Image title

If you click the system diagnostics link you will see two tabs of useful information. The first has memory usage and garbage collection.

The System tab has your usage for FlowFile and Content Repositories, processors and process load.

For more details, check out the following references.


Learn to design and build better data-rich applications with this free eBook from O’Reilly. Brought to you by Mesosphere DC/OS.

nifi ,errors ,big data

Opinions expressed by DZone contributors are their own.


Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.


{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}