Remove the double logging for open trace file failure from the TraceEvent cache based implementation

Description

Contributor guide

Tech stack

cpp

Domain

database

Issue type

refactor

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

2

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

clear

Prerequisites

C++ knowledgeFamiliarity with FoundationDB trace system

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

60

Research direction

The issue requires removing double logging for trace file open failure. The new issue reporting mechanism was introduced in PR #2605, so the old TraceEvent cache based implementation can be removed. Look for the code that handles trace file open failure in the TraceEvent cache and remove the redundant logging. The relevant file is likely in the trace related source files of FoundationDB. The maintainers have provided a clear direction; no further investigation needed.