yugabyte/yugabyte-db

[docdb] Add new per tablet UI for tracking WAL segments

Open

#7,648 opened on Mar 15, 2021

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C (1,003 forks)batch import
area/docdbgood first issuehelp wantedkind/enhancementpriority/medium

Repository metrics

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

Description

Jira Link: DB-2343 We could use a simple per tablet UI where we showcase what are the WAL segments for a given tablet. This could track both count, sizes and maybe even some metadata, like we do for rocksdb.

Per tablet overview UI: :9000/tablet?id=1ca0296435284c90a94f59453be30715 Per tablet rocksdb UI: :9000/rocksdb?id=1ca0296435284c90a94f59453be30715

We could also enhance the /tables and /tablets views, with a Num WAL segments column.

In steady state, these numbers should be pretty low, but when we are dealing with failed pears, fallen behind replication, or in the xCluster solution, some delay between the 2 clusters, this could be pretty useful for high level overview.

cc @amitanandaiyer @rahuldesirazu

Contributor guide

Research direction
Study the existing per tablet rocksdb UI at `/rocksdb` and implement a similar view for WAL segments, showing count, sizes, and metadata. The UI should be accessible at `/tablet?id=<tablet id>` and optionally add a 'Num WAL segments' column to `/tables` and `/tablets` views.
Tech stack
cgoreact
Domain
backendfrontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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 programmingWeb UI developmentYugabyteDB internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20