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.

Failed to obtain value from ZooKeeper for component with ID with exception code CONNECTIONLOSS

New Contributor

p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 18.0px Menlo; color: #28fe14; background-color: #000000; background-color: rgba(0, 0, 0, 0.9)} span.s1 {font-variant-ligatures: no-common-ligatures} span.Apple-tab-span {white-space:pre} ListS3[id=df273570-dabc-17e4-b2a8-4570af7a9770] Failed to restore processor state; yielding

2017-03-09 14:32:37,324 ERROR [Timer-Driven Process Thread-1] Failed to obtain value from ZooKeeper for component with ID df273570-dabc-17e4-b2a8-4570af7a9770 with exception code CONNECTIONLOSS

at org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.getState( ~[na:na]

at org.apache.nifi.controller.state.StandardStateManager.getState( ~[na:na]

at ~[nifi-aws-processors-1.1.1.jar:1.1.1]

at ~[nifi-aws-processors-1.1.1.jar:1.1.1]

at org.apache.nifi.processor.AbstractProcessor.onTrigger( [nifi-api-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_102]

at java.util.concurrent.FutureTask.runAndReset( [na:1.8.0_102]

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301( [na:1.8.0_102]

at java.util.concurrent.ScheduledThreadPoolExecutor$ [na:1.8.0_102]

at java.util.concurrent.ThreadPoolExecutor.runWorker( [na:1.8.0_102]

at java.util.concurrent.ThreadPoolExecutor$ [na:1.8.0_102]

at [na:1.8.0_102]

Caused by: org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss for /nifi/components/df273570-dabc-17e4-b2a8-4570af7a9770

at org.apache.zookeeper.KeeperException.create( ~[na:na]

at org.apache.zookeeper.KeeperException.create( ~[na:na]

at org.apache.zookeeper.ZooKeeper.getData( ~[na:na]

at org.apache.zookeeper.ZooKeeper.getData( ~[na:na]

at org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider.getState( ~[na:na]

... 15 common frames omitted


Master Guru
@Kuntesh Bharucha

Are you using NiFi's embedded ZK or an external ZK?

Have you configured the state-management.xml file with the connection string for your ZK nodes?


In a NiFi cluster, ZK is used to maintain the cluster wide sate of some processors. Those processors will attempt to use the state manager even if it has not been setup correctly or at all.



New Contributor

Hi Matt,

Thanks for your reply. I'm using external zk and was using private IP in Later, when i changed the log level to DEBUG, I got to know that nifi was unable to detect that IP. It was throwing Invalid IP address validation error. Figured out a way of passing public IP since we are going through company's proxy layer. It started working fine.

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