[jira] [Updated] (KAFKA-10348) Consider consolidation of broker to controller communication
[ https://issues.apache.org/jira/browse/KAFKA-10348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen updated KAFKA-10348: Description: Right now, we made forwarding and AlterISR into separate channels to make non-blocking behavior for each other. However, the controller queue is single threaded without prioritization for various requests, so only separating connections may not really help unblocking the AlterISR when forwarding request is taking indefinite time. In long term, we want to see if it is possible to consolidate these two with a systematic logical change on the controller side to ensure AlterISR always have higher priority. After auto topic creation is done, there was more need for this consolidation. was:Right now, we made forwarding and AlterISR into separate channels to make non-blocking behavior for each other. However, the controller queue is single threaded without prioritization for various requests, so only separating connections may not really help unblocking the AlterISR when forwarding request is taking indefinite time. In long term, we want to see if it is possible to consolidate these two with a systematic logical change on the controller side to ensure AlterISR always have higher priority. > Consider consolidation of broker to controller communication > > > Key: KAFKA-10348 > URL: https://issues.apache.org/jira/browse/KAFKA-10348 > Project: Kafka > Issue Type: Sub-task >Reporter: Boyang Chen >Priority: Major > > Right now, we made forwarding and AlterISR into separate channels to make > non-blocking behavior for each other. However, the controller queue is single > threaded without prioritization for various requests, so only separating > connections may not really help unblocking the AlterISR when forwarding > request is taking indefinite time. In long term, we want to see if it is > possible to consolidate these two with a systematic logical change on the > controller side to ensure AlterISR always have higher priority. > > After auto topic creation is done, there was more need for this consolidation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KAFKA-10348) Consider consolidation of broker to controller communication
[ https://issues.apache.org/jira/browse/KAFKA-10348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen updated KAFKA-10348: Description: Right now, we made forwarding and AlterISR into separate channels to make non-blocking behavior for each other. However, the controller queue is single threaded without prioritization for various requests, so only separating connections may not really help unblocking the AlterISR when forwarding request is taking indefinite time. In long term, we want to see if it is possible to consolidate these two with a systematic logical change on the controller side to ensure AlterISR always have higher priority. (was: In the bridge release broker, the UpdateFeatures should be redirected to the active controller instead of relying on admin client discovery.) > Consider consolidation of broker to controller communication > > > Key: KAFKA-10348 > URL: https://issues.apache.org/jira/browse/KAFKA-10348 > Project: Kafka > Issue Type: Sub-task >Reporter: Boyang Chen >Priority: Major > > Right now, we made forwarding and AlterISR into separate channels to make > non-blocking behavior for each other. However, the controller queue is single > threaded without prioritization for various requests, so only separating > connections may not really help unblocking the AlterISR when forwarding > request is taking indefinite time. In long term, we want to see if it is > possible to consolidate these two with a systematic logical change on the > controller side to ensure AlterISR always have higher priority. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KAFKA-10348) Consider consolidation of broker to controller communication
[ https://issues.apache.org/jira/browse/KAFKA-10348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen updated KAFKA-10348: Summary: Consider consolidation of broker to controller communication (was: Redirect UpdateFeatures to the controller) > Consider consolidation of broker to controller communication > > > Key: KAFKA-10348 > URL: https://issues.apache.org/jira/browse/KAFKA-10348 > Project: Kafka > Issue Type: Sub-task >Reporter: Boyang Chen >Priority: Major > > In the bridge release broker, the UpdateFeatures should be redirected to the > active controller instead of relying on admin client discovery. -- This message was sent by Atlassian Jira (v8.3.4#803005)
