[
https://issues.apache.org/jira/browse/KAFKA-13758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17511447#comment-17511447
]
Sree Vaddi commented on KAFKA-13758:
------------------------------------
Work Around:
- restart the broker node. ({*}tried and worked{*})
- clear the lock file of offset / partition / consumer / consumer group in zk
data.folder.
> Exclusive locking in
> kafka.coordinator.group.GroupMetadata.inLock(GroupMetadata.scala:227
> -----------------------------------------------------------------------------------------
>
> Key: KAFKA-13758
> URL: https://issues.apache.org/jira/browse/KAFKA-13758
> Project: Kafka
> Issue Type: Bug
> Environment: Azure
> Reporter: Sree Vaddi
> Priority: Major
>
> {quote} [2022-03-22 15:15:03,127] *ERROR* [GroupMetadataManager brokerId=#]
> Appending metadata message for group ... failed due to unexpected *error:*
> _org.apache.kafka.common.errors.UnknownServerException_
> (kafka.coordinator.group.GroupMetadataManager){quote}
> Probably Issues is here: CoreUtils.scala inLock()
> /**
> * Execute the given function inside the lock
> */
> def inLock[T](lock: Lock)(fun: => T): T = {
> lock.lock()
> try {
> fun
> } finally {
> lock.unlock()
> }
> }
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
