[
https://issues.apache.org/jira/browse/KAFKA-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905391#comment-14905391
]
Ashish K Singh commented on KAFKA-2573:
---------------------------------------
I think the test is failing due to a reason it is not intending to test, or is
it. I am not saying that we should not be catching such issues, my question is
that should we be failing mirror-maker test due to an issue with consumer
shutdown? May be we should. I am fine either ways, but just something we should
agree upon.
If we choose to let the test fail, I can change the PR to just make it fail
fast instead of waiting for 10 minutes.
> Mirror maker system test hangs and eventually fails
> ---------------------------------------------------
>
> Key: KAFKA-2573
> URL: https://issues.apache.org/jira/browse/KAFKA-2573
> Project: Kafka
> Issue Type: Bug
> Reporter: Ashish K Singh
> Assignee: Ashish K Singh
>
> Due to changes made in KAFKA-2015, handling of {{--consumer.config}} has
> changed, more details is specified on KAFKA-2467. This leads to the exception.
> {code}
> Exception in thread "main" java.lang.NoSuchMethodError:
> java.util.concurrent.ConcurrentHashMap.keySet()Ljava/util/concurrent/ConcurrentHashMap$KeySetView;
> at kafka.utils.Pool.keys(Pool.scala:77)
> at
> kafka.consumer.FetchRequestAndResponseStatsRegistry$.removeConsumerFetchRequestAndResponseStats(FetchRequestAndResponseStats.scala:69)
> at
> kafka.metrics.KafkaMetricsGroup$.removeAllConsumerMetrics(KafkaMetricsGroup.scala:189)
> at
> kafka.consumer.ZookeeperConsumerConnector.shutdown(ZookeeperConsumerConnector.scala:200)
> at kafka.consumer.OldConsumer.stop(BaseConsumer.scala:75)
> at kafka.tools.ConsoleConsumer$.process(ConsoleConsumer.scala:98)
> at kafka.tools.ConsoleConsumer$.run(ConsoleConsumer.scala:57)
> at kafka.tools.ConsoleConsumer$.main(ConsoleConsumer.scala:41)
> at kafka.tools.ConsoleConsumer.main(ConsoleConsumer.scala)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
