Page History

...

1. The user sends a DeleteMirror request with the mirror name.
2. The controller validates that the mirror is empty (no topics assigned) or all its partitions are in STOPPED state.
3. If valid, the controller tombstones the mirror configuration in the cluster metadata log, removing all ConfigRecord entries for the mirror.
4. All mirror state entries in __mirror_state for this mirror are cleaned up.
5. Any remaining coordinator state is shut down, source cluster connections are closed, and the mirror name becomes available for reuse.
6. After deletion, failback using this mirror configuration is no longer possible.

List Mirrors

...

1. The user sends ListMirrorsRequest to any broker (no parameters required).

2. The broker handler gets all configured mirror partitions from, which reads from the in memory metadata cache.
3. For each authorized mirror, the broker returns: mirror name, source cluster ID, source bootstrap servers, and topic count.
4. No metadata records are written. This is a read only operation against the local metadata cache.

...

Code Block

{ "apiKey": 104, "type": "response", "name": "DeleteMirrorResponse", // Version 0 is the initial version. "validVersions": "0", "flexibleVersions": "0+", "fields": [ { "name": "ThrottleTimeMs", "type": "int32", "versions": "0+", "about": "The duration in milliseconds for which the request was throttled due to a quota violation, or zero if the request did not violate any quota." }, { "name": "ErrorCode", "type": "int16", "versions": "0+", "about": "The error code, or 0 if there was no error." }, { "name": "ErrorMessage", "type": "string", "versions": "0+", "nullableVersions": "0+", "about": "The error message, or null if there was no error." } ] }

ListMirrors

Returns the current mirror names and their associated topic counts in the cluster. It also includes source cluster ID and bootstrap server.

...