Generatetablefetch processor error

[#1]

Having issues with the generatetablefetch and QueryDatabaseTable processors. They are not returning any data and I see the error "Failed to retrieve observed maximum values from the State Manager" in the Nifi Processor Error tooltip. If I use the executeSQL processor with the same DB connection pool against the same table, everything works fine. This makes me feel it's not a connectivity issue to the Database.

I see the following error in my nifi-app.log:

11:42:09,908 ERROR [Timer-Driven Process Thread-5] o.a.n.p.standard.GenerateTableFetch GenerateTableFetch[id=aec91163-015a-1000-ffff-fffffd91354d] Failed to retrieve observed maximum values from the State Manager. Will not perform query until this is accomplished. 2017-03-08 11:42:09,908 ERROR [Timer-Driven Process Thread-5] o.a.n.p.standard.GenerateTableFetch java.io.IOException: Failed to obtain value from ZooKeeper for component with ID aec91163-015a-1000-ffff-fffffd91354d at org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.getState(ZooKeeperStateProvider.java:423) ~[nifi-framework-core-1.1.1.jar:1.1.1] at org.apache.nifi.controller.state.StandardStateManager.getState(StandardStateManager.java:63) ~[nifi-framework-core-1.1.1.jar:1.1.1] at org.apache.nifi.processors.standard.GenerateTableFetch.onTrigger(GenerateTableFetch.java:137) ~[nifi-standard-processors-1.1.1.jar:1.1.1] at org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1099) [nifi-framework-core-1.1.1.jar:1.1.1] at org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136) [nifi-framework-core-1.1.1.jar:1.1.1] at org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47) [nifi-framework-core-1.1.1.jar:1.1.1] at org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:132) [nifi-framework-core-1.1.1.jar:1.1.1] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_121] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_121] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_121] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_121] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_121] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_121] at java.lang.Thread.run(Thread.java:745) [na:1.8.0_121] Caused by: java.net.UnknownHostException: >denatb3wlwbl07.cloud.my-company.org at java.net.InetAddress.getAllByName0(InetAddress.java:1280) ~[na:1.8.0_121] at java.net.InetAddress.getAllByName(InetAddress.java:1192) ~[na:1.8.0_121] at java.net.InetAddress.getAllByName(InetAddress.java:1126) ~[na:1.8.0_121] at org.apache.zookeeper.client.StaticHostProvider.<init>(StaticHostProvider.java:61) ~[zookeeper-3.4.6.jar:3.4.6-1569965] at org.apache.zookeeper.ZooKeeper.<init>(ZooKeeper.java:445) ~[zookeeper-3.4.6.jar:3.4.6-1569965] at org.apache.zookeeper.ZooKeeper.<init>(ZooKeeper.java:380) ~[zookeeper-3.4.6.jar:3.4.6-1569965] at org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.getZooKeeper(ZooKeeperStateProvider.java:170) ~[nifi-framework-core-1.1.1.jar:1.1.1] at org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.getState(ZooKeeperStateProvider.java:403) ~[nifi-framework-core-1.1.1.jar:1.1.1] ... 13 common frames omitted

[#2]

Did you find a solution for this? I am also facing the same issue.

Initially I had stand-alone without state management. After configuring it as a cluster node and enabling state management, I am getting this error.

[#3]

https://issues.apache.org/jira/browse/NIFI-3875

[#4]

The cause of the exception above is:

Caused by: java.net.UnknownHostException: >denatb3wlwbl07.cloud.my-company.org

Make sure that the clustered state manager is configured in state-management.xml:

<cluster-provider>  
<id>zk-provider</id>  
<class>org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider</class>  
<property name="Connect String"></property>  
<property name="Root Node">/nifi</property>  
<property name="Session Timeout">10 seconds</property>  
<property name="Access Control">Open</property>  
</cluster-provider>

The value for the connect string will be your ZK quorum like "host1:2181,host2:2181,host3:2181" and make sure that all of your NiFi nodes can ping host1, host2, and host3.

In the above stacktrace, the NiFi nodes cannot resolve

denatb3wlwbl07.cloud.my-company.org

[#5]

Thanks, that helped.