Closed
Conversation
|
kafka-trunk-git-pr #457 FAILURE |
|
kafka-trunk-git-pr #458 FAILURE |
mumrah
pushed a commit
to mumrah/kafka
that referenced
this pull request
Oct 8, 2019
As per the new Slack changes we want all the notifications from bots which are not immediately actionable to go to a different channel. Moving the jenkins build alerts to #kafka-warn
omkreddy
pushed a commit
to omkreddy/kafka
that referenced
this pull request
Jan 7, 2020
As per the new Slack changes we want all the notifications from bots which are not immediately actionable to go to a different channel. Moving the jenkins build alerts to #kafka-core-warn. See following doc for the new policy: https://docs.google.com/document/d/1yGTN5FmzQcqwGV5AVymlj2O_pQjAYGbr_jf-F2_WwmY/edit#
wyuka
pushed a commit
to wyuka/kafka
that referenced
this pull request
Jan 21, 2022
…vents (apache#226) TICKET = LIKAFKA-40059 LI_DESCRIPTION = With li combined request feature, a combined response will cause the controller to enqueue an event of LeaderAndIsrResponseReceived, regardless of whether the combined request contains LeaderAndIsr Request or not. As a result, a LI combined request with only metadata update would end up generating an empty LeaderAndIsrResponseReceived event in the controller queue when the response is received by the controller. Since the controller may send out "metadata update requests" to all live brokers, it fills up the controller queue with empty LeaderAndIsrResponseReceived events quickly (e.g., a single metadata update request can generate X LeaderAndIsrResponseReceived events in the controller queue, where X = number of live brokers in the cluster). EXIT_CRITERIA = MANUAL ["when li combined request/response is no longer needed"]
wyuka
pushed a commit
to wyuka/kafka
that referenced
this pull request
Mar 16, 2022
…vents (apache#226) TICKET = LIKAFKA-40059 LI_DESCRIPTION = With li combined request feature, a combined response will cause the controller to enqueue an event of LeaderAndIsrResponseReceived, regardless of whether the combined request contains LeaderAndIsr Request or not. As a result, a LI combined request with only metadata update would end up generating an empty LeaderAndIsrResponseReceived event in the controller queue when the response is received by the controller. Since the controller may send out "metadata update requests" to all live brokers, it fills up the controller queue with empty LeaderAndIsrResponseReceived events quickly (e.g., a single metadata update request can generate X LeaderAndIsrResponseReceived events in the controller queue, where X = number of live brokers in the cluster). EXIT_CRITERIA = MANUAL ["when li combined request/response is no longer needed"]
wyuka
pushed a commit
to wyuka/kafka
that referenced
this pull request
Mar 28, 2022
…vents (apache#226) TICKET = LIKAFKA-40059 LI_DESCRIPTION = With li combined request feature, a combined response will cause the controller to enqueue an event of LeaderAndIsrResponseReceived, regardless of whether the combined request contains LeaderAndIsr Request or not. As a result, a LI combined request with only metadata update would end up generating an empty LeaderAndIsrResponseReceived event in the controller queue when the response is received by the controller. Since the controller may send out "metadata update requests" to all live brokers, it fills up the controller queue with empty LeaderAndIsrResponseReceived events quickly (e.g., a single metadata update request can generate X LeaderAndIsrResponseReceived events in the controller queue, where X = number of live brokers in the cluster). EXIT_CRITERIA = MANUAL ["when li combined request/response is no longer needed"]
wyuka
pushed a commit
to wyuka/kafka
that referenced
this pull request
Jun 16, 2022
…vents (apache#226) TICKET = LIKAFKA-40059 LI_DESCRIPTION = With li combined request feature, a combined response will cause the controller to enqueue an event of LeaderAndIsrResponseReceived, regardless of whether the combined request contains LeaderAndIsr Request or not. As a result, a LI combined request with only metadata update would end up generating an empty LeaderAndIsrResponseReceived event in the controller queue when the response is received by the controller. Since the controller may send out "metadata update requests" to all live brokers, it fills up the controller queue with empty LeaderAndIsrResponseReceived events quickly (e.g., a single metadata update request can generate X LeaderAndIsrResponseReceived events in the controller queue, where X = number of live brokers in the cluster). EXIT_CRITERIA = MANUAL ["when li combined request/response is no longer needed"]
udaynpusa
pushed a commit
to mapr/kafka
that referenced
this pull request
Jan 30, 2024
davide-armand
pushed a commit
to aiven/kafka
that referenced
this pull request
Dec 1, 2025
Workflows can be disabled manually on GitHub and don't have this field to disable.
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
2 participants
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.