Page History

...

A barrier control batch called MIRROR_PID_RESET is written to the destination partition's log during the STOPPING  -> STOPPED transition, after truncation is completed, but before the partition becomes writable. The kafka-dump-log.sh will be updated to decode this new control record type.

The original pid mapping logic is updated to skip it for positive PIDs, making it idempotent.

Barrier Schema

...

The key is a standard control record key (version=0, type=7) per existing ControlRecordType format. The value is a new MirrorPidResetRecord schema.

...

{
  "type": "data",
  "name": "MirrorPidResetRecord",
  "validVersions": "0",
  "flexibleVersions": "0+",
  "fields": [
    { "name": "Version", "type": "int16", "versions": "0",
      "about": "The version of the mirror PID reset record."},
    { "name": "SourceClusterId", "type": "string", "versions": "0",
      "about": "The source cluster UUID for verification."},
    { "name": "TimestampMs", "type": "int64", "versions": "0",
      "about": "Wall-clock time when the barrier was written."}
  ]
}

When ProducerStateManager encounters a When ProducerStateManager encounters a MIRROR_PID_RESET batch during normal append or during recovery (LogSegment.recover replays all batches):                                                                                                                                                          

...