Namespace: RdKafka

Begin internal error codes

Received message is incorrect

Bad/unknown compression

Broker is going away

Generic failure

Broker transport failure

Critical system resource

Failed to resolve broker

Produced message timed out

Reached the end of the topic+partition queue on the broker. Not really an error. This event is disabled by default, see the enable.partition.eof configuration property.

Permanent: Partition does not exist in cluster.

File or filesystem error

Permanent: Topic does not exist in cluster.

All broker connections are down.

Invalid argument, or invalid configuration

Operation timed out

Queue is full

ISR count < required.acks

Broker node update

SSL error

Waiting for coordinator to become available.

Unknown client group

Operation in progress

Previous operation in progress, wait for it to finish.

This operation would interfere with an existing subscription

Assigned partitions (rebalance_cb)

Revoked partitions (rebalance_cb)

Conflicting use

Wrong state

Unknown protocol

Not implemented

Authentication failure

No stored offset

Outdated

Timed out in queue

Feature not supported by broker

Awaiting cache update

Operation interrupted

Key serialization error

Value serialization error

Key deserialization error

Value deserialization error

Partial response

Modification attempted on read-only object

No such entry / item not found

Read underflow

Invalid type

Retry operation

Purged in queue

Purged in flight

Fatal error: see RdKafka::Handle::fatal_error()

Inconsistent state

Gap-less ordering would not be guaranteed if proceeding

Maximum poll interval exceeded

Unknown broker

Functionality not configured

Instance has been fenced

Application generated error

Assignment lost

No operation performed

No offset to automatically reset to

Partition log truncation detected

End internal error codes

Unknown broker error

Success

Offset out of range

Invalid message

Unknown topic or partition

Invalid message size

Leader not available

Not leader for partition

Request timed out

Broker not available

Replica not available

Message size too large

StaleControllerEpochCode

Offset metadata string too large

Broker disconnected before response received

Coordinator load in progress

Group coordinator load in progress

Coordinator not available

Group coordinator not available

Not coordinator

Not coordinator for group

Invalid topic

Message batch larger than configured server segment size

Not enough in-sync replicas

Message(s) written to insufficient number of in-sync replicas

Invalid required acks value

Specified group generation id is not valid

Inconsistent group protocol

Invalid group.id

Unknown member

Invalid session timeout

Group rebalance in progress

Commit offset data size is not valid

Topic authorization failed

Group authorization failed

Cluster authorization failed

Invalid timestamp

Unsupported SASL mechanism

Illegal SASL state

Unuspported version

Topic already exists

Invalid number of partitions

Invalid replication factor

Invalid replica assignment

Invalid config

Not controller for cluster

Invalid request

Message format on broker does not support request

Policy violation

Broker received an out of order sequence number

Broker received a duplicate sequence number

Producer attempted an operation with an old epoch

Producer attempted a transactional operation in an invalid state

Producer attempted to use a producer id which is not currently assigned to its transactional id

Transaction timeout is larger than the maximum value allowed by the broker's max.transaction.timeout.ms

Producer attempted to update a transaction while another concurrent operation on the same transaction was ongoing

Indicates that the transaction coordinator sending a WriteTxnMarker is no longer the current coordinator for a given producer

Transactional Id authorization failed

Security features are disabled

Operation not attempted

Disk error when trying to access log file on the disk

The user-specified log directory is not found in the broker config

SASL Authentication failed

Unknown Producer Id

Partition reassignment is in progress

Delegation Token feature is not enabled

Delegation Token is not found on server

Specified Principal is not valid Owner/Renewer

Delegation Token requests are not allowed on this connection

Delegation Token authorization failed

Delegation Token is expired

Supplied principalType is not supported

The group is not empty

The group id does not exist

The fetch session ID was not found

The fetch session epoch is invalid

No matching listener

Topic deletion is disabled

Leader epoch is older than broker epoch

Leader epoch is newer than broker epoch

Unsupported compression type

Broker epoch has changed

Leader high watermark is not caught up

Group member needs a valid member ID

Preferred leader was not available

Consumer group has reached maximum size

Static consumer fenced by other consumer with same group.instance.id.

Eligible partition leaders are not available

Leader election not needed for topic partition

No partition reassignment is in progress

Deleting offsets of a topic while the consumer group is subscribed to it

Broker failed to validate record

There are unstable offsets that need to be cleared

Throttling quota has been exceeded

There is a newer producer with the same transactionalId which fences the current one

Request illegally referred to resource that does not exist

Request illegally referred to the same resource twice

Requested credential would not meet criteria for acceptability

Indicates that the either the sender or recipient of a voter-only request is not one of the expected voters

Invalid update version

Unable to update finalized features due to server error

Request principal deserialization failed during forwarding