apache / apache/druid

Better tracking of SeekableStreamSupervisor status after reset

Open
#8,317 0 comments 0 reactions 0 assignees View on GitHub
Area - Streaming Ingestion Improvement
Dominant language
Java
Stars
14.1k
Forks
3.8k
Avg merge
2d 58m
Merged PRs (30d)
233

Description

[The `SeekableStreamSupervisor` throws an exception after it successfully resets the offset for a partition](https://github.com/apache/incubator-druid/blob/master/indexing-service/src/main/java/org/apache/druid/indexing/seekablestream/supervisor/SeekableStreamSupervisor.java#L2520-L2524). This looks strange to me because it's not really an exceptional case. I think it's throwing an exception to show to druid operators that the reset happened using the API introduced in #7428 which seems not very useful though. It would be probably better to show the time when the most recent reset happened.

Contributor guide

Open the contributing guide

Research direction

Start in indexing-service/src/main/java/org/apache/druid/indexing/seekablestream/supervisor/SeekableStreamSupervisor.java around lines 2520-2524, where the exception follows a successful partition offset reset. Review the reset API introduced in #7428 and determine how the latest reset time should be exposed to Druid operators. Done means the reset status is tracked with its most recent time instead of being reported as an exceptional case.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.