[
https://issues.apache.org/jira/browse/FLINK-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15024131#comment-15024131
]
Robert Metzger commented on FLINK-3067:
---------------------------------------
If I'm not mistaken, it seems that we are still using the wrong zookeeper
client:
{code}
[INFO] +- org.apache.flink:flink-connector-kafka:jar:1.0-SNAPSHOT:compile
[INFO] | \- org.apache.kafka:kafka_2.10:jar:0.8.2.0:compile
[INFO] | +- org.apache.kafka:kafka-clients:jar:0.8.2.0:compile
[INFO] | | \- net.jpountz.lz4:lz4:jar:1.2.0:compile
[INFO] | +- com.yammer.metrics:metrics-core:jar:2.2.0:compile
[INFO] | +- org.apache.zookeeper:zookeeper:jar:3.4.6:compile
[INFO] | | +- jline:jline:jar:0.9.94:compile
[INFO] | | | \- junit:junit:jar:3.8.1:compile
[INFO] | | \- io.netty:netty:jar:3.7.0.Final:compile
[INFO] | \- com.101tec:zkclient:jar:0.3:compile
{code}
Let me further investigate this...
> Kafka source fails during checkpoint notifications with NPE
> -----------------------------------------------------------
>
> Key: FLINK-3067
> URL: https://issues.apache.org/jira/browse/FLINK-3067
> Project: Flink
> Issue Type: Bug
> Reporter: Gyula Fora
>
> While running a job with many kafka sources I experienced the following error
> during the checkpoint notifications:
> java.lang.RuntimeException: Error while confirming checkpoint
> at org.apache.flink.runtime.taskmanager.Task$2.run(Task.java:935)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
> at
> org.I0Itec.zkclient.ZkConnection.writeDataReturnStat(ZkConnection.java:115)
> at org.I0Itec.zkclient.ZkClient$10.call(ZkClient.java:817)
> at org.I0Itec.zkclient.ZkClient.retryUntilConnected(ZkClient.java:675)
> at org.I0Itec.zkclient.ZkClient.writeDataReturnStat(ZkClient.java:813)
> at org.I0Itec.zkclient.ZkClient.writeData(ZkClient.java:808)
> at org.I0Itec.zkclient.ZkClient.writeData(ZkClient.java:777)
> at kafka.utils.ZkUtils$.updatePersistentPath(ZkUtils.scala:332)
> at kafka.utils.ZkUtils.updatePersistentPath(ZkUtils.scala)
> at
> org.apache.flink.streaming.connectors.kafka.internals.ZookeeperOffsetHandler.setOffsetInZooKeeper(ZookeeperOffsetHandler.java:112)
> at
> org.apache.flink.streaming.connectors.kafka.internals.ZookeeperOffsetHandler.commit(ZookeeperOffsetHandler.java:80)
> at
> org.apache.flink.streaming.connectors.kafka.FlinkKafkaConsumer.notifyCheckpointComplete(FlinkKafkaConsumer.java:563)
> at
> org.apache.flink.streaming.api.operators.AbstractUdfStreamOperator.notifyOfCompletedCheckpoint(AbstractUdfStreamOperator.java:176)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.notifyCheckpointComplete(StreamTask.java:478)
> at org.apache.flink.runtime.taskmanager.Task$2.run(Task.java:931)
> ... 5 more
> 06:23:28,373 INFO org.apache.flink.runtime.executiongraph.ExecutionGraph
> - Source: Kafka[event.rakdos.log] (1/1) (d79e6b7a25b1ac307d2e0c8
> This resulted in the job crashing and getting stuck during cancelling which
> subsequently lead to having to restart the cluster.
> This might be a zookeeper issue but we should be able to handle it (catch the
> exception maybe).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
