Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

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

The open source HPCC Systems platform is a proven, easy to use solution for managing data at scale. Visit our Easy Guide to learn more about this completely free platform, test drive some code in the online Playground, and get started today.

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.

Reference:

Managing data at scale doesn’t have to be hard. Find out how the completely free, open source HPCC Systems platform makes it easier to update, easier to program, easier to integrate data, and easier to manage clusters. Download and get started today.

Topics:
nifi ,errors ,big data

Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}