DUNE-DAQ / DUNE-DAQ/logging

disappearing messages when disk is full

Open
#25 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug help wanted invalid
Dominant language
C++
Stars
0
Forks
0
Avg merge
30m
Merged PRs (30d)
1

Description

@wesketchum noticed that sometimes when the logs are written on a disk that is full, messages simply stop being written, without any ERS Issues (or any kind of exception) being raised by the system.

It has been noticed that ERSIssues continue to flow to kafka when this happens. So the problem is not super urgent, but this can clearly impact the possibility of navigating the history of the system.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by tracing the log-writing path under a full disk and compare it with the ERSIssue-to-Kafka path; done means disk-full failures no longer silently drop messages and an ERS issue or exception is raised.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
observability-sre
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.