[
https://issues.apache.org/jira/browse/KAFKA-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989074#comment-14989074
]
Hannu Valtonen commented on KAFKA-2730:
---------------------------------------
No security features were in use in this particular setup. Here are the config
settings:
"default.replication.factor": 2,
"log.cleaner.enable": "true",
"log.retention.bytes": 4 * units.Gi,
"log.retention.check.interval.ms": 300000,
"log.retention.hours": 168,
"log.segment.bytes": 200 * units.Mi,
"num.io.threads": 8,
"num.network.threads": 8,
"num.partitions": 1,
"num.replica.fetchers": 4,
"num.recovery.threads.per.data.dir": 1,
"zookeeper.connection.timeout.ms": 6000
As an unrelated sidenote on security features I tried setting up SSL a while
back but somehow when more than one broker was added the interbroker
communication collapsed for whatever reason. The idea was to actually try to
get that working now but then I ran into this. :) Once this one gets sorted
I'll give that another spin and open issues if I find any.
I'll try to reproduce this today and attach some logs.
> partition-reassignment tool stops working due to error in registerMetric
> ------------------------------------------------------------------------
>
> Key: KAFKA-2730
> URL: https://issues.apache.org/jira/browse/KAFKA-2730
> Project: Kafka
> Issue Type: Bug
> Components: core
> Reporter: Jun Rao
> Assignee: Guozhang Wang
> Priority: Blocker
> Fix For: 0.9.0.0
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
