-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploying DeathStarBenchmark/Social-Network (thrift protocol) #423
Comments
@yizhengx I'm not certain if Besides, does the Aeraki Thrift demo work in your environment? |
@zhaohuabing Thanks for your reply!
Yes, that works well.
Here's the config_dump/listeners for user-timeline-service in social-network benchmark |
Update: I can manually replace the tcp network filter with aeraki metaprotocol proxy for inbound traffic using the following envoy filter configuration:
This serves as a workaround to recognize other layer-7 protocols, but it would be great for me to understand if I configure things wrong or any other reason that causes the root problems. Thanks for your help! |
@yizhengx Aeraki would automatically create an |
Hi there, we're doing research on microservice and now working on deploying DeathStarBenchmark/Social-Network (using thrift RPC) on Aeraki. We just deploy Aeraki using
make demo
to install istio, aeraki and some examples. Then we deploy social-network benchmark by first labeling namespace then using helm-chart with port name as 'tcp-metaprotocol-thrift-xxx' for protocol discovery.Example user-timeline-service definition:
I checked the istioctl proxy-status which looks fine where listeners are using codec.thrift
However, the traces from the istio-proxy doesn't seem to recognize the protocol
The expected traces from aeraki thrift example looks like
Q1: Any suggestion to fix the problem? Or is there anybody using Aeraki built-in protocols to deploy their own applications?
Q2: Another point I don't understand: for mongodb service, I didn't change the port name to anything related to metaprotocol, but the 'istioctl proxy-status' shows the same output as the service like user-timeline-service I shown before.
The service definition for mongodb is the following:
Thanks! Looking forward to your support and help.
The text was updated successfully, but these errors were encountered: