Re: KIP-800: Add reason to LeaveGroupRequest

[Sophie Blee-Goldman]

This sounds great, thanks David.

One thought: what do you think about doing something similar for the
JoinGroup request?

When you only have broker logs and not client logs, it's somewhere between
challenging and
impossible to determine the reason for a rebalance that was triggered
explicitly by the client or
even the user. For example, when a followup rebalance is requested to
assign the revoked
partitions after a cooperative rebalance. Or any of the many reasons we
trigger a rebalance
in Kafka Streams, via the #enforceRebalance API.

Perhaps we could add a parameter to that method as such:

public void enforceRebalance(final String reason);

Then we can add that to the JoinGroup request/ConsumerProtocol. Not only
would it help to
log this reason on the broker side, the information about who requested the
rebalance and why
could be extremely useful to have available to the group leader/partition
assignor on the client
side.

Cheers,
Sophie

On Fri, Nov 12, 2021 at 10:05 AM Ismael Juma  wrote:

> Thanks David, this is a worthwhile improvement. Quick question, why did we
> pick a tagged field here?
>
> Ismael
>
> On Thu, Nov 11, 2021, 8:32 AM David Jacot 
> wrote:
>
> > Hi folks,
> >
> > I'd like to discuss this very small KIP which proposes to add a reason
> > field
> > to the LeaveGroupRequest in order to let the broker know why a member
> > left the group. This would be really handy for administrators.
> >
> > KIP: https://cwiki.apache.org/confluence/x/eYyqCw
> >
> > Cheers,
> > David
> >
>

[GitHub] [kafka-site] jsancio merged pull request #381: MINOR: Add Jose as an Apache Kafka committter

[GitBox]

jsancio merged pull request #381:
URL: https://github.com/apache/kafka-site/pull/381


   


-- 
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: dev-unsubscr...@kafka.apache.org

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

[DISCUSS] KIP-798 Add possibility to write kafka headers in Kafka Console Producer

[Florin Akermann]

https://cwiki.apache.org/confluence/display/KAFKA/KIP-798%3A+Add+possibility+to+write+kafka+headers+in+Kafka+Console+Producer

Jenkins build is back to normal : Kafka » kafka-2.6-jdk8 #142

[Apache Jenkins Server]

See 

Re: KIP-800: Add reason to LeaveGroupRequest

[Ismael Juma]

Thanks David, this is a worthwhile improvement. Quick question, why did we
pick a tagged field here?

Ismael

On Thu, Nov 11, 2021, 8:32 AM David Jacot 
wrote:

> Hi folks,
>
> I'd like to discuss this very small KIP which proposes to add a reason
> field
> to the LeaveGroupRequest in order to let the broker know why a member
> left the group. This would be really handy for administrators.
>
> KIP: https://cwiki.apache.org/confluence/x/eYyqCw
>
> Cheers,
> David
>

[jira] [Created] (KAFKA-13453) Query: Kafka source port for publishing messages

[Sheriff (Jira)]

Sheriff created KAFKA-13453:
---

 Summary: Query: Kafka source port for publishing messages
 Key: KAFKA-13453
 URL: https://issues.apache.org/jira/browse/KAFKA-13453
 Project: Kafka
  Issue Type: Task
  Components: producer 
Reporter: Sheriff


When message is getting published to kafka topic, bootstrapserver address is 
port is required. While publishing Kafka uses TCP connection so target port 
would be bootstrap server port what would be *source port* for establish TCP 
connection?

Is source port slected dynamically or any configuration is present?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Kafka Schema-Registry Multiple Clusters

[Rishikesh Bamdale]

Hi Team,

Is there any way to create two different schema-registry cluster for same 
kafka-cluster, also if possible what're the steps to be performed?
Also, if possible how to differentiate between multiple clusters and how 
subject names will work.



Thanks,
Rishikesh.

RE: [VOTE] 2.7.2 RC0

[Marcel Stör]

Apache Kafka 2.7.2 is a bugfix release and 26 issues, as well as
CVE-2021-38153, have been fixed since 2.7.1.

Release notes for the 2.7.2 release:
https://home.apache.org/~mimaison/kafka-2.7.2-rc0/RELEASE_NOTES.html


The release notes don't mention CVE-2021-38153 (yet?).

--
Marcel Stör, https://frightanic.com
My PGP key: https://frightanic.com/pgp/
Twitter: https://twitter.com/frightanic


OpenPGP_signature
Description: OpenPGP digital signature

[jira] [Created] (KAFKA-13452) MM2 creates invalid checkpoint when offset mapping is not available

[Daniel Urban (Jira)]

Daniel Urban created KAFKA-13452:


 Summary: MM2 creates invalid checkpoint when offset mapping is not 
available
 Key: KAFKA-13452
 URL: https://issues.apache.org/jira/browse/KAFKA-13452
 Project: Kafka
  Issue Type: Improvement
  Components: mirrormaker
Reporter: Daniel Urban


MM2 checkpointing reads the offset-syncs topic to create offset mappings for 
committed consumer group offsets. In some corner cases, it is possible that a 
mapping is not available in offset-syncs - in that case, MM2 simply copies the 
source offset, which might not be a valid offset in the replica topic at all.

One possible situation is if there is an empty topic in the source cluster with 
a non-zero endoffset (e.g. retention already removed the records), and a 
consumer group which has a committed offset set to the end offset. If 
replication is configured to start replicating this topic, it will not have an 
offset mapping available in offset-syncs (as the topic is empty), causing MM2 
to copy the source offset.

This can cause issues when auto offset sync is enabled, as the consumer group 
offset can be potentially set to a high number. MM2 never rewinds these 
offsets, so even when there is a correct offset mapping available, the offset 
will not be updated correctly.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[RESULTS] [VOTE] Release Kafka version 2.7.2

[Mickael Maison]

This vote passes with 6 +1 votes (3 bindings) and no 0 or -1 votes.

+1 votes
PMC Members:
* Bill Bejeck
* Manikumar Reddy
* Konstantine Karantasis

Committers:
* Tom Bentley

Community:
* Israel Ekpo
* Luke Chen

0 votes
* No votes

-1 votes
* No votes

Vote thread:
https://lists.apache.org/thread/whzns1rj8ythxtfyz18hog1m3y6l215d

I'll continue with the release process and the release announcement
will follow in the next few days.

Mickael

[RESULTS] [VOTE] Release Kafka version 2.6.3

[Mickael Maison]

This vote passes with 5 +1 votes (3 bindings) and no 0 or -1 votes.

+1 votes
PMC Members:
* Bill Bejeck
* Manikumar Reddy
* Konstantine Karantasis

Committers:
* Tom Bentley

Community:
* Israel Ekpo

0 votes
* No votes

-1 votes
* No votes

Vote thread:
https://lists.apache.org/thread/o5zsmhw2lys4zcdlmx2lmvffoznz7r3d

I'll continue with the release process and the release announcement
will follow in the next few days.

Mickael