关于应用元数据的存储膨胀问题
Open
type/discussion
- Dominant language
- Java
- Stars
- 41.6k
- Forks
- 26.4k
- Avg merge
- 15h 13m
- Merged PRs (30d)
- 4
Description
问题描述: 假如某个应用发布了几十次,每次发布都修改了某个dubbo接口,这样应用元数据都会计算出不同的一个revision,存储在元数据中心中,那其实真正用到的元数据是最新一次发布的元数据,之前几十个revision也用不到了,在很多应用频繁发布服务的情况下可能会导致元数据中心的存储压力,这块有没有好的解决方案?
使用版本dubbo-3.0.10
@AlbumenJ
Contributor guide
Research direction
Start by reviewing how Dubbo 3.0.10 stores application metadata revisions in the metadata center and reproduce the repeated-publish scenario described in the issue. Determine how obsolete revisions are identified and whether removing them preserves the latest metadata; done means an agreed, tested retention or cleanup approach that prevents unbounded storage growth.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100