Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KAFKA-18166: Indefinite timeout when publishing events to RLMM (RemoteLogMetadataManager) #18097

Open
wants to merge 1 commit into
base: trunk
Choose a base branch
from

Conversation

FrankYang0529
Copy link
Member

To prevent RLMM hang on CompletableFuture.get(), add a reasonable timeout on these functions.

Committer Checklist (excluded from commit message)

  • Verify design and implementation
  • Verify test coverage and CI build status
  • Verify documentation (including upgrade notes)

@github-actions github-actions bot added core Kafka Broker tiered-storage Related to the Tiered Storage feature small Small PRs labels Dec 8, 2024
@@ -555,7 +556,7 @@ private void deleteRemoteLogPartition(TopicIdPartition partition) throws RemoteS
new RemoteLogSegmentMetadataUpdate(metadata.remoteLogSegmentId(), time.milliseconds(),
metadata.customMetadata(), RemoteLogSegmentState.DELETE_SEGMENT_STARTED, brokerId))
.collect(Collectors.toList());
publishEvents(deleteSegmentStartedEvents).get();
publishEvents(deleteSegmentStartedEvents).get(1000, TimeUnit.MILLISECONDS);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's better to put timeout to a constant field to avoid magic numbers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Kafka Broker small Small PRs tiered-storage Related to the Tiered Storage feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants