BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//sf26-agenda//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
BEGIN:VEVENT
UID:SESS-62@sf26-agenda
DTSTAMP:20261103T101708Z
DTSTART:20261104T220000Z
DTEND:20261104T224500Z
SUMMARY:Migrating to KIP-848 and the new assignors\, Live: A Visual Guide
LOCATION:Room 2000
DESCRIPTION:David Jacot\, Lianet Magrans\n\nKIP-848 is GA\, but the migrati
 on is still ahead of most teams. At its core is the protocol switch: the C
 lassic rebalance protocol is on a deprecation path (KIP-1274). But there's
  a second story that lands directly on applications: assignors. KIP-848 mo
 ves assignment from a client-side\, leader-driven election to broker-hoste
 d pluggable assignors\, so teams with specific assignment needs face a rea
 l question: what do I do about my custom\, client-side assignor\, and how 
 do I move it to the new world in the 4.x releases? This session covers the
  assignor migration in as much depth as the protocol switch itself. We'll 
 demystify how assignment works in the KIP-848 era — the coordinator's ta
 rget-assignment model and incremental reconciliation — then walk the mov
 e off classic client-side strategies to the broker side: how the built-in 
 assignors map onto the two server-side ones\, how to implement a custom as
 signor through the new server assignor SPI and enable it via group-level a
 nd client configuration\, and how to observe\, debug\, and roll back the r
 esult with the new logs and metrics. We'll ground it all in a live visual 
 simulator of the group coordinator and its members — watching a real Cla
 ssic group migrate on stage\, with heartbeats\, epochs\, reconciliation\, 
 and offset commits visible as they happen — alongside the protocol essen
 tials: config changes\, rolling upgrade and rollback\, and the post-GA fol
 low-ups. Takeaways: A clear\, visual model of the new protocol\, and a con
 crete playbook for the assignor migration that comes with it — mapping t
 he built-ins\, implementing and enabling a custom server-side assignor\, a
 nd verifying the result before 5.0\, without sacrificing the resilience an
 d operability benefits of KIP-848. Who is it for: Consumer-group owners pl
 anning their KIP-848 migration. Platform and application engineers running
  Kafka at scale. Teams with custom assignors that need to move to the brok
 er-side assignors.
URL:https://sf26.rmoff.net/s/migrating-to-kip-848-and-the-new-assignors-liv
 e-a-visual-62
END:VEVENT
END:VCALENDAR