You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by GitBox <gi...@apache.org> on 2022/07/07 08:02:30 UTC

[GitHub] [kafka] dengziming commented on pull request #12274: KAFKA-13959: Controller should unfence Broker with busy metadata log

dengziming commented on PR #12274:
URL: https://github.com/apache/kafka/pull/12274#issuecomment-1177222867

   > Do you have a diff for this solution?
   @jsancio  I havn't flesh it, the basic idea is shown in this PR, only read up to `Isolation.COMMITTED` when reading from observer and invoke `fetchPurgatory.maybeComplete(highWatermark.offset, currentTimeMs)` on `onUpdateLeaderHighWatermark`.
   
   
   
   > maybe we can try the original proposed one?
   @showuon This solution can only take effect if the problem is that the heartbeat period is much bigger than NoOpRecord, it may not work now since main the problem is from `RaftClient.fetchPurgatory`, so we should try a new solution.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: jira-unsubscribe@kafka.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org