[
https://issues.apache.org/jira/browse/STORM-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470353#comment-16470353
]
Stig Rohde Døssing commented on STORM-3067:
-------------------------------------------
[~RAbreu] This is expected behavior and shouldn't affect processing. See
https://issues.apache.org/jira/browse/STORM-2542 (I know the fix version lists
only 2.0.0/1.2.0, but we backported to 1.1.2 as well in
https://github.com/apache/storm/pull/2549).
Basically we are letting the spout manage which processes consume which
partitions, rather than letting Kafka control it, and that's why you're seeing
a different output. When it's referring to "active members" it means
KafkaConsumers that are currently letting Kafka control their subscriptions.
Since the spout controls the subscription manually, its consumer isn't
considered an active member.
> Kafka Spout has no active members in consumer group
> ---------------------------------------------------
>
> Key: STORM-3067
> URL: https://issues.apache.org/jira/browse/STORM-3067
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-kafka-client
> Affects Versions: 1.1.2
> Reporter: Rui Abreu
> Priority: Major
>
> Using Kafka 10.2.1, two different behaviours were observed:
> Storm 1.1.0 =>
> {code}
> /opt/kafka/bin/kafka-consumer-groups.sh --bootstrap-server localhost:9092
> --group test.topic.consumer-group --describe
> Note: This will only show information about consumers that use the Java
> consumer API (non-ZooKeeper-based consumers).
> TOPIC PARTITION CURRENT-OFFSET LOG-END-OFFSET LAG CONSUMER-ID HOST CLIENT-ID
> test.topic 0 85186604 85186607 3
> consumer-2-27a77d1b-e851-47a4-954e-4953ea612b72 /X.X.X.X consumer-2
> {code}
>
> Storm 1.1.2 =>
> {code:java}
> /opt/kafka/bin/kafka-consumer-groups.sh --bootstrap-server localhost:9092
> --group test.topic.consumer-group --describe
> Note: This will only show information about consumers that use the Java
> consumer API (non-ZooKeeper-based consumers).
> Consumer group 'test.topic.consumer-group' has no active members.
> TOPIC PARTITION CURRENT-OFFSET LOG-END-OFFSET LAG CONSUMER-ID HOST CLIENT-ID
> test.topic 0 85202473 85202475 2 -{code}
> Despite this behaviour, the topology continues to consume messages and commit
> offsets to Kafka. It's unclear if this lack of active clients on the consumer
> group affects the normal functioning of the Spout.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
