StarRocks/starrocks

Optimize lock granularity at com.starrocks.service.FrontendServiceImpl#describeTable

Closed

#66,515 opened on Dec 9, 2025

View on GitHubContributor guide
 (1 comment) (2 reactions) (1 assignee)Java (1,246 forks)batch import
good first issueno-issue-activitytype/enhancement

Repository metrics

Stars
 (5,717 stars)
PR merge metrics
 (Avg merge 1d 5h) (1,000 merged PRs in 30d)

Description

Enhancement

https://github.com/StarRocks/starrocks/blob/e1d514b432df55f4e2843affb776e71b48db92a2/fe/fe-core/src/main/java/com/starrocks/service/FrontendServiceImpl.java#L821

Executing frequent queries like SELECT * FROM information_schema.columns WHERE xxxx triggers com.starrocks.service.FrontendServiceImpl#describeTable, which unnecessarily employs a database lock, potentially causing performance degradation.

Contributor guide

Research direction
Analyze the current database lock in describeTable method and propose a more fine grained locking strategy, possibly using read locks or row level locks to reduce contention.
Tech stack
java
Domain
backenddatabase
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.
1-2 days
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.
Mostly clear
Prerequisites
Javadatabase locking
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50