apache / apache/servicecomb-java-chassis
INFO Required: Edge gateway service routing to mesher Side car proxy
還沒有人認領這個 Issue。
- 主要語言
- Java
- 星號
- 1.9k
- 分支
- 813
- 平均合併
- 8 天 23 小時
- 30 天內合併 PR
- 1
描述
Below is the system flow i am experimenting with,
====================================
Edge service ( developed with java chassis SDK) <-> Side car Proxy connector (built with Service-mesh and service ports configured to point to legacy application) --> Legacy Servlet application
====================================================
I can successfully able to run mesher as side car proxy and get it registered in the service center. I can also able to hit provider API's (servlet based application) via mesher side car proxy.
However I can't able to route to the provider application via mesher side car proxy from the edge gateway.
Below is the routing configuration in edge service.
- I am using
URLMappedEdgeDispatcher. - And
legacyis name of the side car provider mesher microservice with which it has been registered in the service center.
dispatcher:
edge:
url:
enabled: true
mappings:
legacy:
path: "/legacy/.*"
microserviceName: legacy
prefixSegmentCount: 0
versionRule: 0.0.0+ `
I am getting this error on runtime
**2022-11-10 17:38:46,606 [ERROR] [transport-vert.x-eventloop-thread-3] - locate path failed, status:Not Found, http method:GET, path:/calculator/bmi/, microserviceName:calculator (OperationLocator.java:72)**
@liubao68 It seems URLMappedEdgeDispatcher is not the right one to use here as it does schema based routing. Please help point me how we can achieve this? are there any other dispatchers which would effectively route traffic from edge service to side car proxy mesher connector?
貢獻指南
這個儲存庫沒有索引到貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
從 URLMappedEdgeDispatcher 和所示的 edge 路由設定開始,接著追蹤 /calculator/bmi/ 和 microserviceName calculator 的 OperationLocator 錯誤。重現從 edge 到 Mesher 的路由流程,並將其與已成功註冊的 legacy sidecar 路徑進行比較。當 edge gateway 能透過 Mesher sidecar 將請求路由至 legacy provider 時,即表示完成。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- java
- 領域
- backend, networking
- Issue 類型
- 缺陷
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 25/100