apache / apache/servicecomb-java-chassis
INFO Required: Edge gateway service routing to mesher Side car proxy
- Langage dominant
- Java
- Étoiles
- 1.9k
- Forks
- 814
- Merge moyen
- 8 j 23 h
- PR mergées (30 j)
- 1
Description
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 `legacy` is name of the side car provider mesher microservice with which it has been registered in the service center.
``` http:
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?
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
Commencez par URLMappedEdgeDispatcher et la configuration de routage de l’edge présentée, puis suivez l’erreur de OperationLocator pour /calculator/bmi/ et microserviceName calculator. Reproduisez le flux de routage de l’edge vers Mesher et comparez-le au chemin du sidecar legacy enregistré avec succès. La tâche est terminée lorsque la passerelle edge achemine les requêtes vers le fournisseur legacy via le sidecar Mesher.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- java
- Domaine
- backend, networking
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100