Support Questions

Find answers, ask questions, and share your expertise
Check out our newest addition to the community, the Cloudera Data Analytics (CDA) group hub.

Generatetablefetch processor error

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 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( ~[nifi-framework-core-1.1.1.jar:1.1.1] at org.apache.nifi.controller.state.StandardStateManager.getState( ~[nifi-framework-core-1.1.1.jar:1.1.1] at org.apache.nifi.processors.standard.GenerateTableFetch.onTrigger( ~[nifi-standard-processors-1.1.1.jar:1.1.1] at org.apache.nifi.controller.StandardProcessorNode.onTrigger( [nifi-framework-core-1.1.1.jar:1.1.1] at [nifi-framework-core-1.1.1.jar:1.1.1] at [nifi-framework-core-1.1.1.jar:1.1.1] at org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$ [nifi-framework-core-1.1.1.jar:1.1.1] at java.util.concurrent.Executors$ [na:1.8.0_121] at java.util.concurrent.FutureTask.runAndReset( [na:1.8.0_121] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301( [na:1.8.0_121] at java.util.concurrent.ScheduledThreadPoolExecutor$ [na:1.8.0_121] at java.util.concurrent.ThreadPoolExecutor.runWorker( [na:1.8.0_121] at java.util.concurrent.ThreadPoolExecutor$ [na:1.8.0_121] at [na:1.8.0_121] Caused by: > at ~[na:1.8.0_121] at ~[na:1.8.0_121] at ~[na:1.8.0_121] at org.apache.zookeeper.client.StaticHostProvider.<init>( ~[zookeeper-3.4.6.jar:3.4.6-1569965] at org.apache.zookeeper.ZooKeeper.<init>( ~[zookeeper-3.4.6.jar:3.4.6-1569965] at org.apache.zookeeper.ZooKeeper.<init>( ~[zookeeper-3.4.6.jar:3.4.6-1569965] at org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.getZooKeeper( ~[nifi-framework-core-1.1.1.jar:1.1.1] at org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.getState( ~[nifi-framework-core-1.1.1.jar:1.1.1] ... 13 common frames omitted



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.


The cause of the exception above is:

Caused by: >

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

<property name="Connect String"></property>  
<property name="Root Node">/nifi</property>  
<property name="Session Timeout">10 seconds</property>  
<property name="Access Control">Open</property>  

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


Thanks, that helped.

Take a Tour of the Community
Don't have an account?
Your experience may be limited. Sign in to explore more.