yugabyte/yugabyte-db

[DocDB] Track memory for traces when enable_tracing is turned on

Open

#19,511 opened on Oct 12, 2023

View on GitHub
 (0 comments) (0 reactions) (1 assignee)C (1,003 forks)batch import
area/docdbgood first issuekind/enhancementpriority/medium

Repository metrics

Stars
 (8,229 stars)
PR merge metrics
 (Avg merge 17d 21h) (92 merged PRs in 30d)

Description

Jira Link: DB-8306

Description

When tracing is enabled by turning on the gflag - enable_tracing, significant amount of memory is used up by traces (Proportional to the number of active connections/RPCs). This memory is untracked and can appear as a leak. Its better to track the memory corresponding to the traces.

Issue Type

kind/enhancement

Warning: Please confirm that this issue does not contain any sensitive information

  • I confirm this issue does not contain any sensitive information.

Contributor guide

Research direction
Understand how tracing allocates memory and identify where to add memory tracking hooks.
Tech stack
ccpp
Domain
databasebackendinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++gflagsMemory Management
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30