Exception | Description | Analysis and Explanation |
UnknownServerException | An unknown error occurred while the server was processing a request. | In earlier versions, this error may be returned due to traffic control. In later versions, it may be caused by a bug in the server. |
RecordTooLargeException | Messages were too large. | Current configuration: message.max.bytes=1000012. |
InvalidRequiredAcksException | The acks parameter in the producer configuration was invalid. | - |
InconsistentGroupProtocolException | The protocols for the Group were inconsistent. | Check whether the consumer and connector were configured with the same group.id. They use different protocols and cannot join the same group. |
InvalidGroupIdException | The consumer group ID was invalid. | It is recommended to use the characters (lower-case letters (a-z), upper-case letters (A-Z), digits (0-9), periods (.), underscores (_), and hyphens (-)) and keep the length under 128. |
InvalidTopicException | The topic was invalid. | After the automatic topic creation option is enabled, this exception will be returned if the topic used by the client is invalid. Check whether the topic contains invalid characters or exceeds the length limit. |
InvalidSessionTimeoutException | The session.timeout.ms parameter configured by the consumer was invalid. | Minimum value currently allowed on the server: group.min.session.timeout.ms=6000; maximum value: group.max.session.timeout.ms=300000. |
InvalidCommitOffsetSizeException | Committed offset information was too large and exceeded the maximum message size, failing to be written to __consumer_offsets. | Current configuration: message.max.bytes=1000012. |
OffsetMetadataTooLarge | The offset commit request contained too large metadata. | Server configuration: offset.metadata.max.bytes=4096. |
UnsupportedVersionException | The broker did not support requests from clients of this version. | It is recommended to use clients of version 0.10.2.x. |
Exception | Description | Analysis and Explanation |
TimeoutException | Requests timed out. | If the request timeout is reported on the first connection attempt, first check whether the address is correct and use telnet to confirm network connectivity. If this exception is thrown occasionally during program operation, the cause may be network jitter. |
CorruptRecordException | Messages were invalid. | The cause may be a failure to pass the CRC check or an invalid data size. Additionally, if the compression method uses GZIP or compression is used in versions earlier than 0.9, it may also cause this error. |
UnknownTopicOrPartitionException | The topic or partition did not exist. | Check whether the corresponding topic has been created in the console. Note: The client produces or consumes messages via TopicName, rather than TopicId. Additionally, if the client lacks the permission to access a topic, it will also report that the topic does not exist. |
LeaderNotAvailableException | The partition did not have a leader. | When a topic is just created, the server has not yet elected a suitable leader. At this time, this error is returned to the client. The client will automatically retry to obtain the leader information. This exception only occurs in earlier versions and has been fixed in version 0.10.2.1. |
NotLeaderForPartitionException | The leader of the partition was unavailable. | Since the client caches the metadata of topics, when the leader is switched in a partition, production or consumption requests may still be sent to the old leader. In such cases, this error is returned to the client, and the client automatically updates the metadata information. |
NetworkException | The client connection was closed by the server. | The network is abnormal, or the number of connections exceeds the limit. |
NotEnoughReplicasException | The number of ISRs was insufficient. | During data writes, the number of ISRs in a partition is smaller than the min.insync.replicas configured for the topic, possibly due to ISR jitter. |
NotEnoughReplicasAfterAppendException | After data was written to the broker locally, ISR jitter occurred, resulting in a failure to meet min.insync.replicas. | - |
BrokerNotAvailableError | No leader was found for the partition. | Since the client caches the metadata of topics, when the leader is switched in a partition, production or consumption requests may still be sent to the old leader. In such cases, this error is returned to the client, and the client automatically updates the metadata information. After a leader switch, new production requests are sent to the old leader. After an error is reported, the requests are automatically redirected to the new leader. In theory, this will not affect the integrity of data writing and consumption. |
NotLeaderForPartitionError | No leader was found for the partition. | Since the client caches the metadata of topics, when the leader is switched in a partition, production or consumption requests may still be sent to the old leader. In such cases, this error is returned to the client, and the client automatically updates the metadata information. After a leader switch, new production requests are sent to the old leader. After an error is reported, the requests are automatically redirected to the new leader. In theory, this will not affect the integrity of data writing and consumption. |
Exception | Description | Analysis and Explanation |
OffsetOutOfRangeException | The offset passed when the consumer pulled messages was out of range. | If the client has set an offset reset policy (earliest or latest), it will reset the offset according to the policy. Otherwise, the user program needs to handle this exception. |
GroupLoadInProgressException | The corresponding coordinator of the ConsumerGroup was loading. | This exception may occur transiently during server upgrades. The client will retry automatically. |
GroupCoordinatorNotAvailableException | The coordinator was unavailable. | This exception may occur transiently during server upgrades. The client will retry automatically. |
NotCoordinatorForGroupException | The current node was not the coordinator of the ConsumerGroup. The coordinator was migrated to another node. | This exception may occur transiently during server upgrades. The client will retry automatically. |
IllegalGenerationException | The generation of the ConsumerGroup was invalid. | The heartbeat may have timed out, or a new consumer has joined. The consumer will automatically retry to rejoin the ConsumerGroup. |
RebalanceInProgressException | The ConsumerGroup was undergoing a rebalance. | The heartbeat may have timed out, or a new consumer has joined. The consumer will automatically retry to rejoin the ConsumerGroup. |
Esta página foi útil?
Você também pode entrar em contato com a Equipe de vendas ou Enviar um tíquete em caso de ajuda.
comentários