kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Cheng (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-6054) ERROR "SubscriptionInfo - unable to decode subscription data: version=2" when upgrading from to
Date Wed, 11 Oct 2017 16:42:00 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200571#comment-16200571

James Cheng commented on KAFKA-6054:

Here is my conversation with [~mjsax] from the Confluent Slack channel:

James Cheng [9:16 AM] 
Does this stack trace mean anything to anyone? It happened when we upgraded a kafka streams
app from to
^ @mjsax, if you have any time to look. Thanks.

Matthias J Sax 
[9:20 AM] 
That makes sense. We bumped the internal version number when adding IQ feature -- thus, it
seems you cannot mix instances for both version.

Seems, we messed up the upgrade path :disappointed:

If you can, you would need to stop all old instances, before starting with the new version.

Can you also open a JIRA for this?

Thus, rolling bounces to upgrade should actually work -- is this what you are doing?

James Cheng [9:27 AM] 
Yes, we're doing a rolling upgrade. We had (at one point, at least) both instances running.

I imagine that if the versions crashed, then restarted running, then they
would be fine because they are all the same version at that point, right?

Matthias J Sax 
[9:27 AM] 

James Cheng [9:27 AM] 
Cool, thanks.

Matthias J Sax 
[9:28 AM] 
Anyway. Please file a JIRA -- upgrading should always work without this error.

James Cheng [9:29 AM] 
I'll file the JIRA.

Matthias J Sax 
[9:30 AM] 

> ERROR "SubscriptionInfo - unable to decode subscription data: version=2" when upgrading
from to
> -----------------------------------------------------------------------------------------------------------------
>                 Key: KAFKA-6054
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6054
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions:
>            Reporter: James Cheng
> We upgraded an app from kafka-streams to We did a rolling upgrade
of the app, so that one point, there were both instances and
instances running. 
> We observed the following stack trace:
> {code}
> 2017-10-11 07:02:19.964 [StreamThread-3] ERROR o.a.k.s.p.i.a.SubscriptionInfo -
> unable to decode subscription data: version=2
> org.apache.kafka.streams.errors.TaskAssignmentException: unable to decode
> subscription data: version=2
>         at org.apache.kafka.streams.processor.internals.assignment.SubscriptionInfo.decode(SubscriptionInfo.java:113)
>         at org.apache.kafka.streams.processor.internals.StreamPartitionAssignor.assign(StreamPartitionAssignor.java:235)
>         at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.performAssignment(ConsumerCoordinator.java:260)
>         at org.apache.kafka.clients.consumer.internals.AbstractCoordinator.onJoinLeader(AbstractCoordinator.java:404)
>         at org.apache.kafka.clients.consumer.internals.AbstractCoordinator.access$900(AbstractCoordinator.java:81)
>         at org.apache.kafka.clients.consumer.internals.AbstractCoordinator$JoinGroupResponseHandler.handle(AbstractCoordinator.java:358)
>         at org.apache.kafka.clients.consumer.internals.AbstractCoordinator$JoinGroupResponseHandler.handle(AbstractCoordinator.java:340)
>         at org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:679)
>         at org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:658)
>         at org.apache.kafka.clients.consumer.internals.RequestFuture$1.onSuccess(RequestFuture.java:167)
>         at org.apache.kafka.clients.consumer.internals.RequestFuture.fireSuccess(RequestFuture.java:133)
>         at org.apache.kafka.clients.consumer.internals.RequestFuture.complete(RequestFuture.java:107)
>         at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient$RequestFutureCompletionHandler.onComplete(ConsumerNetworkClient.java:426)
>         at org.apache.kafka.clients.NetworkClient.poll(NetworkClient.java:278)
>         at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.clientPoll(ConsumerNetworkClient.java:360)
>         at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:224)
>         at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:192)
>         at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:163)
>         at org.apache.kafka.clients.consumer.internals.AbstractCoordinator.ensureActiveGroup(AbstractCoordinator.java:243)
>         at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.ensurePartitionAssignment(ConsumerCoordinator.java:345)
>         at org.apache.kafka.clients.consumer.KafkaConsumer.pollOnce(KafkaConsumer.java:977)
>         at org.apache.kafka.clients.consumer.KafkaConsumer.poll(KafkaConsumer.java:937)
>         at org.apache.kafka.streams.processor.internals.StreamThread.runLoop(StreamThread.java:295)
>         at org.apache.kafka.streams.processor.internals.StreamThread.run(StreamThread.java:218)
> {code}
> I spoke with [~mjsax] and he said this is a known issue that happens when you have both instances and instances running at the same time, because the internal version
number of the protocol changed when adding Interactive Queries. Matthias asked me to file
this JIRA>

This message was sent by Atlassian JIRA

View raw message