[
https://issues.apache.org/jira/browse/KAFKA-7508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16700187#comment-16700187
]
Jonathan Santilli commented on KAFKA-7508:
------------------------------------------
Kafka Brokers offer good metrics from JMX, you can use your favorite JMX client
to connect to the Brokers JMX port.
Linkedin has good tools to monitor [https://github.com/linkedin/streaming]
Kafka Brokers is a process that runs in your server, you can monitor it as a
normal process (just to check is the Broker is up or not)
But is not just that of course, you need to monitor the Broker from the
application point of view as well and JMX metrics will help you with that.
BTW, if you consider this issue has been solved, let us know to close it,
please.
Cheers!
--
Jonathan
> Kafka broker anonymous disconnected from Zookeeper
> --------------------------------------------------
>
> Key: KAFKA-7508
> URL: https://issues.apache.org/jira/browse/KAFKA-7508
> Project: Kafka
> Issue Type: Task
> Components: admin, config
> Reporter: Sathish Yanamala
> Priority: Blocker
>
> Hello Team,
>
> We are facing below Error , Kafka broker unable to connect Zookeeper , Please
> check and suggest is there any configuration changes required on Kafka Broker.
>
> ERROR:
> 2018-10-15 12:24:07,502 WARN kafka.network.Processor: Attempting to send
> response via channel for which there is no open connection, connection id
> -<Broker IP Address> -:9093--<Broker IP Address> -:47542-25929
> 2018-10-15 12:24:09,428 INFO kafka.coordinator.group.GroupCoordinator:
> [GroupCoordinator 3]: Group KMOffsetCache-xxxxxxx with generation 9 is now
> empty (__consumer_offsets-22)
> 2018-10-15 12:24:09,428 INFO kafka.server.epoch.LeaderEpochFileCache: Updated
> PartitionLeaderEpoch. New: \{epoch:1262, offset:151}, Current: \{epoch:1261,
> offset144} for Partition: __consumer_offsets-22. Cache now contains 15
> entries.
> {color:#d04437}*2018-10-15 12:24:10,905 ERROR kafka.utils.KafkaScheduler:
> Uncaught exception in scheduled task 'highwatermark-checkpoint'*{color}
> {color:#d04437}*java.lang.OutOfMemoryError: Java heap space*{color}
> {color:#d04437} at{color}
> scala.collection.convert.DecorateAsScala$$Lambda$214/xxxxx.get$Lambda(Unknown
> Source)
> at
> java.lang.invoke.LambdaForm$DMH/xxxxxxx.invokeStatic_LL_L(LambdaForm$DMH)
> at
> java.lang.invoke.LambdaForm$MH/xxxxxx.linkToTargetMethod(LambdaForm$MH)
> at
> scala.collection.convert.DecorateAsScala.collectionAsScalaIterableConverter(DecorateAsScala.scala:45)
> at
> scala.collection.convert.DecorateAsScala.collectionAsScalaIterableConverter$(DecorateAsScala.scala:44)
> at
> scala.collection.JavaConverters$.collectionAsScalaIterableConverter(JavaConverters.scala:73)
> at kafka.utils.Pool.values(Pool.scala:85)
> at
> kafka.server.ReplicaManager.nonOfflinePartitionsIterator(ReplicaManager.scala:397)
> at
> kafka.server.ReplicaManager.checkpointHighWatermarks(ReplicaManager.scala:1340)
> at
> kafka.server.ReplicaManager.$anonfun$startHighWaterMarksCheckPointThread$1(ReplicaManager.scala:253)
> at
> kafka.server.ReplicaManager$$Lambda$608/xxxxxx.apply$mcV$sp(Unknown Source)
> at
> kafka.utils.KafkaScheduler.$anonfun$schedule$2(KafkaScheduler.scala:110)
> at
> kafka.utils.KafkaScheduler$$Lambda$269/xxxxxxxx.apply$mcV$sp(Unknown Source)
> at kafka.utils.CoreUtils$$anon$1.run(CoreUtils.scala:61)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>
> Thank you,
> Sathish Yanamala
> M:832-382-4487
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
