Telemetry data may be lost during bootstrap in embedded fast-exit scenarios
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 339
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 52
Description
Description
In embedded mode, there is a risk of losing bootstrap telemetry data due to fast-exit behavior.
Details
After a successful bootstrap, telemetry reporting is scheduled to execute asynchronously with a 1-second delay via ServerGTimer. If an embedded client opens a connection and then exits very quickly, the seekdb instance will exit immediately due to "no clients remaining." This can cause the delayed telemetry task to be canceled before it can execute, resulting in the telemetry data not being reported.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing embedded bootstrap telemetry scheduling through ServerGTimer and the fast-exit path triggered when no clients remain. Reproduce or inspect the one-second delayed task in the embedded scenario, then verify that bootstrap telemetry is reported before the instance exits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100