Mark Bean created NIFI-4716:
-------------------------------
Summary: Provenance query unhandled exception when Node
disconnected
Key: NIFI-4716
URL: https://issues.apache.org/jira/browse/NIFI-4716
Project: Apache NiFi
Issue Type: Bug
Components: Core Framework
Affects Versions: 1.4.0
Reporter: Mark Bean
Scenario: 2-node Cluster with one Node disconnected. Using the UI of the
surviving Node, when attempting a Data Provenance query, a popup error dialog
indicates "Cluster is unable to service request to change flow: Node
<disconnected-node-server:port> is currently disconnected.". This occurs even
before the Provenance Events list is generated.
However, using the UI of the disconnected Node the same Data Provenance query
is attempted. Now, a list of Provenance events is displayed. Then, when
choosing 'View Details', an uncaught exception occurs: "An unexpected error has
occurred. Please check the logs for additional details."
The nifi-user.log indicates:
o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred:
java.lang.NullPointerException. Returning Internal Server Error response
java.lang.NullPointerException: null
at
org.apache.nifi.web.api.ProvenanceEventResource.getProvenanceEvent(ProvenanceEventResource.java:297)
...
First, the error reported by the connected Node is misleading. An attempt to
change the flow has not been made.
Second, recommend the disconnected Node behave as the connected Node and
immediate return an error on an attempt to query provenance. (However, the
error should be more descriptive of the problem as noted above.)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
