StarRocks/starrocks

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

Open

#66515 opened on Dec 9, 2025

View on GitHub
 (0 comments) (2 reactions) (1 assignee)Java (5,717 stars) (1,246 forks)batch import
good first issuetype/enhancement

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

Tech stack
javasql
Domain
performancebackend
Issue type
performance
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-3 hours
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
JavaLocking conceptsStarRocks FE internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Focus on the method `describeTable` in `FrontendServiceImpl.java` (line 821). Understand the current database lock usage and evaluate if a finer grained lock (e.g., table level or row level) can be applied. Review existing unit tests for this method to ensure changes do not break functionality.