DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
...
| Code Block | ||
|---|---|---|
| ||
public enum CoordinatorType {
GROUP((byte) 0),
TRANSACTION((byte) 1),
SHARE((byte) 2),
MIRROR((byte) 3); // New type
} |
Errors
List of protocol-level errors returned in API responses:
...
Mirror Metadata Records
LastMirroredOffsets
...
| Code Block |
|---|
{
"apiKey": 2,
"type": "coordinator-key",
"name": "MirrorPartitionStateKey",
"validVersions": "0",
"flexibleVersions": "none",
"fields": [
{ "name": "MirrorName", "type": "string", "versions": "0",
"about": "The cluster mirror name."}
]
}
{
"apiKey": 2,
"type": "coordinator-value",
"name": "MirrorPartitionStateValue",
"validVersions": "0",
"flexibleVersions": "0+",
"fields": [
{ "name": "TopicName", "type": "string", "versions": "0",
"about": "The topic name."},
{ "name": "Partition", "type": "int32", "versions": "0",
"about": "The partition index."},
{ "name": "State", "type": "int8", "versions": "0+",
"about": "The mirror partition state." }
]
} |
Errors
List of protocol-level errors returned in API responses:
| Error Code | Name | Used By | Context |
|---|---|---|---|
| 3 | UNKNOWN_TOPIC_OR_PARTITION | MirrorMetadataManager | Source topic metadata has errors during sync |
| 15 | COORDINATOR_NOT_AVAILABLE | MirrorCoordinator | Mirror coordinator is not active |
| 31 | CLUSTER_AUTHORIZATION_FAILED | KafkaApis, ControllerApis | Missing authorization for mirror operations |
| 35 | UNSUPPORTED_VERSION | KafkaApis, ControllerApis | Cluster mirroring disabled (mirror.version=0) |
| 38 | INVALID_REPLICATION_FACTOR | ReplicationControlManager | Insufficient brokers for mirror topic replication |
| 39 | INVALID_REPLICA_ASSIGNMENT | ReplicationControlManager | Brokers fenced or in controlled shutdown |
| 42 | INVALID_REQUEST | KafkaApis, ConfigurationControlManager | Validation failures (direct mirror.name modification, mirror disabled, invalid config) |
Configuration
A new configuration resource type is added for cluster mirrors, which is stored in the cluster metadata internal log. Both DescribeConfigs and IncrementalAlterConfigs will be bumped to new versions so that clients can check ApiVersionsResponse to determine whether the broker supports mirror configuration management, rather than having to send a request and interpret the error.
...