[ 
https://issues.apache.org/jira/browse/SAMZA-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jagadish updated SAMZA-1592:
----------------------------
    Description: 
After the 0.11 upgrade, the latest branch in hello-samza (and hence all our 
open-source tutorials that rely on it) are broken. Users who follow the 
tutorial will see this error when starting their job.

 
{code:java}
2018-02-21 10:32:56.604 [main] SyncProducer [INFO] Connected to localhost:9092 
for producing
2018-02-21 10:32:56.604 [main] ClientUtils$ [WARN] Fetching topic metadata with 
correlation id 0 for topics [Set(wikipedia-stats)] from broker 
[BrokerEndPoint(0,localhost,9092)] failed
java.lang.NoSuchMethodError: org.apache.kafka.common.network.NetworkSend: 
method <init>(Ljava/lang/String;[Ljava/nio/ByteBuffer;)V not found
at kafka.network.RequestOrResponseSend.<init>(RequestOrResponseSend.scala:41)
at kafka.network.RequestOrResponseSend.<init>(RequestOrResponseSend.scala:44)
/*
at kafka.network.BlockingChannel.send(BlockingChannel.scala:112)
at kafka.producer.SyncProducer.liftedTree1$1(SyncProducer.scala:80)
at 
kafka.producer.SyncProducer.kafka$producer$SyncProducer$$doSend(SyncProducer.scala:79)
at kafka.producer.SyncProducer.send(SyncProducer.scala:124)
at kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:59)
at kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:94)
at 
org.apache.samza.util.ClientUtilTopicMetadataStore.getTopicInfo(ClientUtilTopicMetadataStore.scala:37)
at 
org.apache.samza.system.kafka.KafkaSystemAdmin.getTopicMetadata(KafkaSystemAdmin.scala:352)
at 
org.apache.samza.system.kafka.KafkaSystemAdmin$$anonfun$getSystemStreamMetadata$2$$anonfun$9.apply(KafkaSystemAdmin.scala:230)
at 
org.apache.samza.system.kafka.KafkaSystemAdmin$$anonfun$getSystemStreamMetadata$2$$anonfun$9.apply(KafkaSystemAdmin.scala:230)
at 
org.apache.samza.system.kafka.TopicMetadataCache$.getTopicMetadata(TopicMetadataCache.scala:52)
at 
org.apache.samza.system.kafka.KafkaSystemAdmin$$anonfun$getSystemStreamMetadata$2.apply(KafkaSystemAdmin.scala:227)
at 
org.apache.samza.system.kafka.KafkaSystemAdmin$$anonfun$getSystemStreamMetadata$2.apply(KafkaSystemAdmin.scala:226)
at 
org.apache.samza.util.ExponentialSleepStrategy.run(ExponentialSleepStrategy.scala:83)
at 
org.apache.samza.system.kafka.KafkaSystemAdmin.getSystemStreamMetadata(KafkaSystemAdmin.scala:225)
at 
org.apache.samza.system.kafka.KafkaSystemAdmin.getSystemStreamMetadata(KafkaSystemAdmin.scala:213)
at 
org.apache.samza.execution.StreamManager.getStreamPartitionCounts(StreamManager.java:82)
at 
org.apache.samza.execution.ExecutionPlanner.updateExistingPartitions(ExecutionPlanner.java:163)
at org.apache.samza.execution.ExecutionPlanner.plan(ExecutionPlanner.java:71)
at 
org.apache.samza.runtime.AbstractApplicationRunner.getExecutionPlan(AbstractApplicationRunner.java:146)
at 
org.apache.samza.runtime.AbstractApplicationRunner.getExecutionPlan(AbstractApplicationRunner.java:124)
at 
org.apache.samza.runtime.LocalApplicationRunner.run(LocalApplicationRunner.java:152)
at 
samza.examples.wikipedia.application.WikipediaZkLocalApplication.main(WikipediaZkLocalApplication.java:51)
{code}

While open-source moved on to using Kafka-0.11, the hello-samza tutorial still 
relies on Kafka 0.10. The fix is to make both these Kafka versions consistent 
by updating the hello-samza tutorial to use Kafka 0.11

  was:
After the 0.11 upgrade, the latest branch in hello-samza (and hence all our 
open-source tutorials that rely on it) are broken. Users who follow the 
tutorial will see this error when starting their job.

 
{code:java}
2018-02-21 10:32:56.604 [main] SyncProducer [INFO] Connected to localhost:9092 
for producing
2018-02-21 10:32:56.604 [main] ClientUtils$ [WARN] Fetching topic metadata with 
correlation id 0 for topics [Set(wikipedia-stats)] from broker 
[BrokerEndPoint(0,localhost,9092)] failed
java.lang.NoSuchMethodError: org.apache.kafka.common.network.NetworkSend: 
method <init>(Ljava/lang/String;[Ljava/nio/ByteBuffer;)V not found
at kafka.network.RequestOrResponseSend.<init>(RequestOrResponseSend.scala:41)
at kafka.network.RequestOrResponseSend.<init>(RequestOrResponseSend.scala:44)
/*
at kafka.network.BlockingChannel.send(BlockingChannel.scala:112)
at kafka.producer.SyncProducer.liftedTree1$1(SyncProducer.scala:80)
at 
kafka.producer.SyncProducer.kafka$producer$SyncProducer$$doSend(SyncProducer.scala:79)
at kafka.producer.SyncProducer.send(SyncProducer.scala:124)
at kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:59)
at kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:94)
at 
org.apache.samza.util.ClientUtilTopicMetadataStore.getTopicInfo(ClientUtilTopicMetadataStore.scala:37)
at 
org.apache.samza.system.kafka.KafkaSystemAdmin.getTopicMetadata(KafkaSystemAdmin.scala:352)
at 
org.apache.samza.system.kafka.KafkaSystemAdmin$$anonfun$getSystemStreamMetadata$2$$anonfun$9.apply(KafkaSystemAdmin.scala:230)
at 
org.apache.samza.system.kafka.KafkaSystemAdmin$$anonfun$getSystemStreamMetadata$2$$anonfun$9.apply(KafkaSystemAdmin.scala:230)
at 
org.apache.samza.system.kafka.TopicMetadataCache$.getTopicMetadata(TopicMetadataCache.scala:52)
at 
org.apache.samza.system.kafka.KafkaSystemAdmin$$anonfun$getSystemStreamMetadata$2.apply(KafkaSystemAdmin.scala:227)
at 
org.apache.samza.system.kafka.KafkaSystemAdmin$$anonfun$getSystemStreamMetadata$2.apply(KafkaSystemAdmin.scala:226)
at 
org.apache.samza.util.ExponentialSleepStrategy.run(ExponentialSleepStrategy.scala:83)
at 
org.apache.samza.system.kafka.KafkaSystemAdmin.getSystemStreamMetadata(KafkaSystemAdmin.scala:225)
at 
org.apache.samza.system.kafka.KafkaSystemAdmin.getSystemStreamMetadata(KafkaSystemAdmin.scala:213)
at 
org.apache.samza.execution.StreamManager.getStreamPartitionCounts(StreamManager.java:82)
at 
org.apache.samza.execution.ExecutionPlanner.updateExistingPartitions(ExecutionPlanner.java:163)
at org.apache.samza.execution.ExecutionPlanner.plan(ExecutionPlanner.java:71)
at 
org.apache.samza.runtime.AbstractApplicationRunner.getExecutionPlan(AbstractApplicationRunner.java:146)
at 
org.apache.samza.runtime.AbstractApplicationRunner.getExecutionPlan(AbstractApplicationRunner.java:124)
at 
org.apache.samza.runtime.LocalApplicationRunner.run(LocalApplicationRunner.java:152)
at 
samza.examples.wikipedia.application.WikipediaZkLocalApplication.main(WikipediaZkLocalApplication.java:51)
{code}




> Hello-Samza latest branch is broken after Kafka 0.11 upgrade in Samza
> ---------------------------------------------------------------------
>
>                 Key: SAMZA-1592
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1592
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Jagadish
>            Assignee: Jagadish
>            Priority: Major
>
> After the 0.11 upgrade, the latest branch in hello-samza (and hence all our 
> open-source tutorials that rely on it) are broken. Users who follow the 
> tutorial will see this error when starting their job.
>  
> {code:java}
> 2018-02-21 10:32:56.604 [main] SyncProducer [INFO] Connected to 
> localhost:9092 for producing
> 2018-02-21 10:32:56.604 [main] ClientUtils$ [WARN] Fetching topic metadata 
> with correlation id 0 for topics [Set(wikipedia-stats)] from broker 
> [BrokerEndPoint(0,localhost,9092)] failed
> java.lang.NoSuchMethodError: org.apache.kafka.common.network.NetworkSend: 
> method <init>(Ljava/lang/String;[Ljava/nio/ByteBuffer;)V not found
> at kafka.network.RequestOrResponseSend.<init>(RequestOrResponseSend.scala:41)
> at kafka.network.RequestOrResponseSend.<init>(RequestOrResponseSend.scala:44)
> /*
> at kafka.network.BlockingChannel.send(BlockingChannel.scala:112)
> at kafka.producer.SyncProducer.liftedTree1$1(SyncProducer.scala:80)
> at 
> kafka.producer.SyncProducer.kafka$producer$SyncProducer$$doSend(SyncProducer.scala:79)
> at kafka.producer.SyncProducer.send(SyncProducer.scala:124)
> at kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:59)
> at kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:94)
> at 
> org.apache.samza.util.ClientUtilTopicMetadataStore.getTopicInfo(ClientUtilTopicMetadataStore.scala:37)
> at 
> org.apache.samza.system.kafka.KafkaSystemAdmin.getTopicMetadata(KafkaSystemAdmin.scala:352)
> at 
> org.apache.samza.system.kafka.KafkaSystemAdmin$$anonfun$getSystemStreamMetadata$2$$anonfun$9.apply(KafkaSystemAdmin.scala:230)
> at 
> org.apache.samza.system.kafka.KafkaSystemAdmin$$anonfun$getSystemStreamMetadata$2$$anonfun$9.apply(KafkaSystemAdmin.scala:230)
> at 
> org.apache.samza.system.kafka.TopicMetadataCache$.getTopicMetadata(TopicMetadataCache.scala:52)
> at 
> org.apache.samza.system.kafka.KafkaSystemAdmin$$anonfun$getSystemStreamMetadata$2.apply(KafkaSystemAdmin.scala:227)
> at 
> org.apache.samza.system.kafka.KafkaSystemAdmin$$anonfun$getSystemStreamMetadata$2.apply(KafkaSystemAdmin.scala:226)
> at 
> org.apache.samza.util.ExponentialSleepStrategy.run(ExponentialSleepStrategy.scala:83)
> at 
> org.apache.samza.system.kafka.KafkaSystemAdmin.getSystemStreamMetadata(KafkaSystemAdmin.scala:225)
> at 
> org.apache.samza.system.kafka.KafkaSystemAdmin.getSystemStreamMetadata(KafkaSystemAdmin.scala:213)
> at 
> org.apache.samza.execution.StreamManager.getStreamPartitionCounts(StreamManager.java:82)
> at 
> org.apache.samza.execution.ExecutionPlanner.updateExistingPartitions(ExecutionPlanner.java:163)
> at org.apache.samza.execution.ExecutionPlanner.plan(ExecutionPlanner.java:71)
> at 
> org.apache.samza.runtime.AbstractApplicationRunner.getExecutionPlan(AbstractApplicationRunner.java:146)
> at 
> org.apache.samza.runtime.AbstractApplicationRunner.getExecutionPlan(AbstractApplicationRunner.java:124)
> at 
> org.apache.samza.runtime.LocalApplicationRunner.run(LocalApplicationRunner.java:152)
> at 
> samza.examples.wikipedia.application.WikipediaZkLocalApplication.main(WikipediaZkLocalApplication.java:51)
> {code}
> While open-source moved on to using Kafka-0.11, the hello-samza tutorial 
> still relies on Kafka 0.10. The fix is to make both these Kafka versions 
> consistent by updating the hello-samza tutorial to use Kafka 0.11



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to