Skip to content

[E2E] group_mode_transactions_test failed with TimeoutException #802

@mooc9988

Description

@mooc9988

client log

ERROR Aborting transaction after catching exception (org.apache.kafka.tools.TransactionalMessageCopier)
org.apache.kafka.common.errors.TimeoutException: Timeout of 60000ms expired before the last committed offset for partitions [input-topic-4, input-topic-5, input-topic-3] could be determined. Try tuning default.api.timeout.ms larger to relax the threshold.

server log

[2024-02-17 16:19:16,205] INFO [ReplicaFetcherManager on broker 1] Removed fetcher for partitions Set(__consumer_offsets-2) (kafka.server.ReplicaFetcherManager)
[2024-02-17 16:19:16,450] INFO [Partition __consumer_offsets-2 broker=1] Log loaded for partition __consumer_offsets-2 with initial high watermark 1136 (kafka.cluster.Partition)

[2024-02-17 16:19:52,047] INFO [GroupCoordinator 1]: Elected as the group coordinator for partition 2 in epoch 2 (kafka.coordinator.group.GroupCoordinator)
[2024-02-17 16:19:52,058] DEBUG [GroupMetadataManager brokerId=1] Started loading offsets and group metadata from __consumer_offsets-2 for epoch 2 (kafka.coordinator.group.GroupMetadataManager)

ducker08 held partition __consumer_offsets-2. Then, it was killed at 16:18:28. After some time, all partitions held by ducker08 were moved to active nodes. __consumer_offsets-2 was moved to ducker07 at 16:19:16 and group data was loaded at 16:19:52. Therefore, 84 seconds had passed since __consumer_offsets-2 was unavailable. As a result, consumer throwed TimeoutException.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions