Closed
Conversation
… Holoman reviewed by Gwen Shapira and Joe Stein
… reviewed by Jun Rao
…in; reviewed by Jun Rao
…t any data cause process to not start; reviewed by Neha Narkhede
…t; patched by Jun Rao; reviewed by Neha Narkhede
…work again; reviewed by Neha Narkhede
…; reviewed by Joel Koshy
…e Spike to 100% when network connection is lost; patched by Ewen Cheslack-Postava; patched by Ewen Cheslack-Postava; reviewed by Jun Rao
…the new java client; patched by Jun Rao; reviewed by Jay Kreps
…pi to the new java client; patched by Jun Rao; reviewed by Neha Narkhede
…ddress patch by Jeff Holoman reviewed by Jay Krepps and Gwen Shapira
…/deserializer api to the new java client; patched by Jun Rao; reviewed by Manikumar Reddy and Neha Narkhede
…ly contains unknown partitions; patched by Jun Rao; reviewed by Neha Narkhede
…ewed by Neha Narkhede and Ewen Cheslack-Postava
… reviewed by Neha Narkhede
…erializer api to the new java client; patched by Jun Rao
…hed by Manikumar Reddy; reviewed by Jay Kreps and Jun Rao
…ence of a jira.ini file, during patch submission; reviewed by Neha Narkhede
… producer more standard; patched by Manikumar Reddy; reviewed by Jun Rao
… false if not explicitly set; patched by Jun Rao; reviewed by Jeol Koshy
…Java API; patched by Jun Rao; reviewed by Jeol Koshy and Sriharsha Chintalapani
…by Jun Rao; reviewed by Jeol Koshy, Neha Narkhede, and Gwen Shapira
…lt is 2; patched by Manikumar Reddy; reviewed by Jun Rao
… fails with TimeoutException while trying to fetch metadata for topic; patched by jaikiran pai; reviewed by Jun Rao
…on; patched by Jun Rao; reviewed by Joe Stein and Sriharsha Chintalapani
…ableByteChannel.read(buffer); patched by Dong Lin; reviewed by Jun Rao
|
kafka-trunk-git-pr #6 FAILURE |
…eritskiy; reviewed by Jun Rao
|
kafka-trunk-git-pr #8 FAILURE |
Member
|
Can you please close this pull request? It's triggering builds in the CI server and we cannot close it ourselves without asking Apache Infra. Thanks! |
…estFromPropsToProps; patched by Jason Gustafson; reviewed by Jun Rao
|
kafka-trunk-git-pr #9 FAILURE |
… Cheslack-Postava; reviewed by Jun Rao
|
kafka-trunk-git-pr #10 FAILURE |
Author: Ismael Juma <ismael@juma.me.uk> Closes #82 from ijuma/kafka-2324 and squashes the following commits: d71bf5c [Ismael Juma] KAFKA-2324; Update to Scala 2.11.7
|
kafka-trunk-git-pr #11 FAILURE |
…ows ZkNodeExistsException; patched by Ashish Singh; reviewed by Sriharsha Chintalapani and Ismael Juma
|
kafka-trunk-git-pr #14 FAILURE |
|
kafka-trunk-git-pr #15 FAILURE |
guozhangwang
referenced
this pull request
in confluentinc/kafka
Aug 5, 2015
Add RocksDB KeyValueStore
resetius
added a commit
to resetius/kafka
that referenced
this pull request
Jun 7, 2016
[LOGBROKER-1543] fix OfflinePartitionLeaderSelector
xiowu0
added a commit
to xiowu0/kafka
that referenced
this pull request
Oct 11, 2019
…pache#42) TICKET = LI_DESCRIPTION = This Patch separates Kafka Controller Node from non-controller (data) Node. Summary of changes: 1)Add “preferred.controller” broker config (its type is boolean) to indicate whether a broker is used as a preferred controller node. 2)Add “allow.preferred.controller.fallback” broker config that determines whether a non-preferred controller node (data node) is allowed to become controller in the absence of preferred controller nodes. If “allow.preferred.controller.fallback” is set to “false”, a non-preferred controller node never tries to become controller, and only preferred controller nodes can be elected as controller. If “allow.preferred.controller.fallback” is set to “true”, a non-preferred controller node tries to elect itself as controller only in the absence of preferred controller node and a non-preferred active controller resigns as controller when it detects any live preferred controller. 3)Add ActivePreferredControllerCount metric to track whether the current broker is preferred controller node and is elected as Kafka controller 4)Add StandbyPreferredControllerCount metric to track whether the current broker is preferred controller node and is not elected as controller. EXIT_CRITERIA = MANUAL [""]
efeg
pushed a commit
to efeg/kafka
that referenced
this pull request
Jan 29, 2020
… cluster model sanity check failure. (apache#42)
satishd
referenced
this pull request
in satishd/kafka
Mar 30, 2020
Fixed local and effective logStartOffset updation when segments are deleted locally but not in the remote tiered storage.
smccauliff
pushed a commit
to smccauliff/kafka
that referenced
this pull request
Oct 8, 2020
…pache#42) TICKET = LI_DESCRIPTION = This Patch separates Kafka Controller Node from non-controller (data) Node. Summary of changes: 1)Add “preferred.controller” broker config (its type is boolean) to indicate whether a broker is used as a preferred controller node. 2)Add “allow.preferred.controller.fallback” broker config that determines whether a non-preferred controller node (data node) is allowed to become controller in the absence of preferred controller nodes. If “allow.preferred.controller.fallback” is set to “false”, a non-preferred controller node never tries to become controller, and only preferred controller nodes can be elected as controller. If “allow.preferred.controller.fallback” is set to “true”, a non-preferred controller node tries to elect itself as controller only in the absence of preferred controller node and a non-preferred active controller resigns as controller when it detects any live preferred controller. 3)Add ActivePreferredControllerCount metric to track whether the current broker is preferred controller node and is elected as Kafka controller 4)Add StandbyPreferredControllerCount metric to track whether the current broker is preferred controller node and is not elected as controller. EXIT_CRITERIA = MANUAL [""]
wyuka
pushed a commit
to wyuka/kafka
that referenced
this pull request
Mar 4, 2022
…pache#42) TICKET = LI_DESCRIPTION = This Patch separates Kafka Controller Node from non-controller (data) Node. Summary of changes: 1) Add "preferred.controller” broker config (its type is boolean) to indicate whether a broker is used as a preferred controller node. 2) Add "allow.preferred.controller.fallback” broker config that determines whether a non-preferred controller node (data node) is allowed to become controller in the absence of preferred controller nodes. If "allow.preferred.controller.fallback” is set to "false”, a non-preferred controller node never tries to become controller, and only preferred controller nodes can be elected as controller. If "allow.preferred.controller.fallback” is set to "true”, a non-preferred controller node tries to elect itself as controller only in the absence of preferred controller node and a non-preferred active controller resigns as controller when it detects any live preferred controller. 3) Add ActivePreferredControllerCount metric to track whether the current broker is preferred controller node and is elected as Kafka controller 4) Add StandbyPreferredControllerCount metric to track whether the current broker is preferred controller node and is not elected as controller. EXIT_CRITERIA = MANUAL [""]
wyuka
pushed a commit
to wyuka/kafka
that referenced
this pull request
Mar 28, 2022
…pache#42) TICKET = LI_DESCRIPTION = This Patch separates Kafka Controller Node from non-controller (data) Node. Summary of changes: 1) Add "preferred.controller” broker config (its type is boolean) to indicate whether a broker is used as a preferred controller node. 2) Add "allow.preferred.controller.fallback” broker config that determines whether a non-preferred controller node (data node) is allowed to become controller in the absence of preferred controller nodes. If "allow.preferred.controller.fallback” is set to "false”, a non-preferred controller node never tries to become controller, and only preferred controller nodes can be elected as controller. If "allow.preferred.controller.fallback” is set to "true”, a non-preferred controller node tries to elect itself as controller only in the absence of preferred controller node and a non-preferred active controller resigns as controller when it detects any live preferred controller. 3) Add ActivePreferredControllerCount metric to track whether the current broker is preferred controller node and is elected as Kafka controller 4) Add StandbyPreferredControllerCount metric to track whether the current broker is preferred controller node and is not elected as controller. EXIT_CRITERIA = MANUAL [""]
wyuka
pushed a commit
to wyuka/kafka
that referenced
this pull request
Jun 16, 2022
…pache#42) TICKET = LI_DESCRIPTION = This Patch separates Kafka Controller Node from non-controller (data) Node. Summary of changes: 1) Add "preferred.controller” broker config (its type is boolean) to indicate whether a broker is used as a preferred controller node. 2) Add "allow.preferred.controller.fallback” broker config that determines whether a non-preferred controller node (data node) is allowed to become controller in the absence of preferred controller nodes. If "allow.preferred.controller.fallback” is set to "false”, a non-preferred controller node never tries to become controller, and only preferred controller nodes can be elected as controller. If "allow.preferred.controller.fallback” is set to "true”, a non-preferred controller node tries to elect itself as controller only in the absence of preferred controller node and a non-preferred active controller resigns as controller when it detects any live preferred controller. 3) Add ActivePreferredControllerCount metric to track whether the current broker is preferred controller node and is elected as Kafka controller 4) Add StandbyPreferredControllerCount metric to track whether the current broker is preferred controller node and is not elected as controller. EXIT_CRITERIA = MANUAL [""]
lianetm
pushed a commit
to lianetm/kafka
that referenced
this pull request
Aug 10, 2023
…ator node is discovered. (apache#42) * Fixing flaky test * ensure coordinator is known. * Update CommitRequestManager.java * Update BaseAsyncConsumerTest.scala
patrik-marton
pushed a commit
to patrik-marton/kafka
that referenced
this pull request
Mar 11, 2025
fvaleri
added a commit
to fvaleri/kafka
that referenced
this pull request
Nov 27, 2025
Minor refactoring
blitzy Bot
pushed a commit
to blitzy-public-samples/blitzy-kafka
that referenced
this pull request
Apr 19, 2026
…apache#3) Remediates 3 MINOR QA findings — all broken anchor fragments in docs/security-audit/findings/07-external-function-callback-misuse.md. The previous anchor fragments used MkDocs-style semantic IDs that do not resolve against GitHub-flavored markdown auto-generated heading slugs. This commit aligns each fragment to the GitHub-computed slug for the target heading. Fixes: * Line 197: #oauth -> apache#32-security--oauth Target: ### 3.2 Security - OAuth (accepted-mitigations.md:201) (double-hyphen comes from the two spaces around the em-dash; the em-dash itself is stripped by the GitHub slug algorithm) * Line 227: #oauth -> apache#32-security--oauth (both visible text and URL) Target: same as Line 197 (second occurrence in the 'Cross-References' section) * Line 232: apache#62-restclient-forwarding -> apache#42-connect-restclient- forwards-the-inbound-authorization-header-to-outbound-worker- peer-calls-062 Target: ### 4.2 Connect RestClient forwards the inbound Authorization header to outbound worker-peer calls (06.2) (findings/06-network-subprocess-access.md:90) (URL fragment updated; visible short identifier retained for readability per QA suggested-fix guidance) Validation: * Runtime re-verification: all 88 anchor-bearing links across the 24 audit markdown files now resolve (0 broken anchors). * File inventory unchanged: 25 files, surgical 6-line diff (3 insertions, 3 deletions). * Visual Architecture Documentation rule preserved: all 7 diagrams still referenced by name across findings and supporting docs. * Audit Only rule preserved: zero source-code modifications; only the audit deliverable under docs/security-audit/ is touched. QA report: QA Final Checkpoint apache#3 - Link Integrity + Cross-References + License Headers (Issues 1-3, all MINOR, all in findings/07).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.