apache / apache/servicecomb-java-chassis

2.1版本 重启的时候有可能会导致 no schema defined

Open
#4,295 8 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
1.9k
Forks
814
Avg merge
8d 23h
Merged PRs (30d)
1

Description

问题现象:
服务重启成功后,调RPC接口会有这个报错
![image](https://github.com/apache/servicecomb-java-chassis/assets/51687046/9cc2f68d-f8e6-49af-aa4c-bad4927dfc0c)

初步分析:
异常时,MicroserviceMeta中对象如下
![image](https://github.com/apache/servicecomb-java-chassis/assets/51687046/b027f739-5776-4d81-9739-070f238e99e5)
正常时,MicroserviceMeta对比
![image](https://github.com/apache/servicecomb-java-chassis/assets/51687046/af381a2c-15e7-4626-8993-4c24c80d81b4)

怀疑是RestEngineSchemaListener 没有正常接收CreateMicroserviceVersionEvent 事件完成处理,求问有没有避免措施,或者其他解决方案

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing RestEngineSchemaListener and CreateMicroserviceVersionEvent handling around the MicroserviceMeta state shown in the report. Reproduce the restart sequence and determine why the schema is missing; done means RPC calls after a successful restart no longer fail with “no schema defined”.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.