Hannu, Could you past the related server-side request logs before this exception thrown if you have any? Particularly, we are interested in the LeaderAndISR request reception traces.
And to clarify, when you "upgrade the system tests with the newest version" you mean all the brokers are using this version right? Guozhang On Tue, Nov 3, 2015 at 7:37 AM, Jun Rao <j...@confluent.io> wrote: > Hannu, > > Thanks for reporting this. Filed > https://issues.apache.org/jira/browse/KAFKA-2730 for further > investigation. > If you have more input, please add it to the jira. > > Jun > > On Tue, Nov 3, 2015 at 6:55 AM, Hannu Valtonen <hannu.valto...@ohmu.fi> > wrote: > > > Hi, > > > > I updated our test system to use Kafka from latest revision > > 7c33475274cb6e65a8e8d907e7fef6e56bc8c8e6 and now I'm seeing: > > > > [2015-11-03 14:07:01,554] ERROR [KafkaApi-2] error when handling request > > > Name:LeaderAndIsrRequest;Version:0;Controller:3;ControllerEpoch:1;CorrelationId:5;ClientId:3;Leaders:BrokerEndPoint(3,192.168.60.168,21769);PartitionState:(5c700e33-9230-4219-a3e1-42574c175d62-logs,0) > > -> > > > (LeaderAndIsrInfo:(Leader:3,ISR:3,LeaderEpoch:1,ControllerEpoch:1),ReplicationFactor:3),AllReplicas:2,3,1) > > (kafka.server.KafkaApis) > > java.lang.IllegalArgumentException: A metric named 'MetricName > > [name=connection-close-rate, group=replica-fetcher-metrics, > > description=Connections closed per second in the window., > > tags={broker-id=3}]' already exists, can't register another one. > > at > org.apache.kafka.common.metrics.Metrics.registerMetric(Metrics.java:285) > > at org.apache.kafka.common.metrics.Sensor.add(Sensor.java:177) > > at org.apache.kafka.common.metrics.Sensor.add(Sensor.java:162) > > at > > > org.apache.kafka.common.network.Selector$SelectorMetrics.<init>(Selector.java:578) > > at org.apache.kafka.common.network.Selector.<init>(Selector.java:112) > > at > kafka.server.ReplicaFetcherThread.<init>(ReplicaFetcherThread.scala:69) > > at > > > kafka.server.ReplicaFetcherManager.createFetcherThread(ReplicaFetcherManager.scala:35) > > at > > > kafka.server.AbstractFetcherManager$$anonfun$addFetcherForPartitions$2.apply(AbstractFetcherManager.scala:83) > > at > > > kafka.server.AbstractFetcherManager$$anonfun$addFetcherForPartitions$2.apply(AbstractFetcherManager.scala:78) > > at > > > scala.collection.TraversableLike$WithFilter$$anonfun$foreach$1.apply(TraversableLike.scala:772) > > at scala.collection.immutable.Map$Map1.foreach(Map.scala:109) > > at > > > scala.collection.TraversableLike$WithFilter.foreach(TraversableLike.scala:771) > > at > > > kafka.server.AbstractFetcherManager.addFetcherForPartitions(AbstractFetcherManager.scala:78) > > at kafka.server.ReplicaManager.makeFollowers(ReplicaManager.scala:791) > > at > > > kafka.server.ReplicaManager.becomeLeaderOrFollower(ReplicaManager.scala:628) > > at kafka.server.KafkaApis.handleLeaderAndIsrRequest(KafkaApis.scala:114) > > at kafka.server.KafkaApis.handle(KafkaApis.scala:71) > > at kafka.server.KafkaRequestHandler.run(KafkaRequestHandler.scala:60) > > at java.lang.Thread.run(Thread.java:745) > > > > This happens when I'm running kafka-reassign-partitions.sh. As a result > in > > the verify command one of the partition reassignments says "is still in > > progress" forever. > > > > I'm wondering if anyone has reported this as a bug previously or should I > > open a new JIRA ticket for this? > > > > - Hannu Valtonen > > > -- -- Guozhang
