Skip to content
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

Question about "classic-rest-service" #184

Open
bookin opened this issue Jul 13, 2021 · 0 comments
Open

Question about "classic-rest-service" #184

bookin opened this issue Jul 13, 2021 · 0 comments

Comments

@bookin
Copy link

bookin commented Jul 13, 2021

In the Survival Guide I see this information for "classic-rest-service":

Microservice Protocol Deployment or StatefulSet Node Pool Assignment Autoscaling Supported Description
classic-rest-service REST/HTTP StatefulSet analytics or system Yes (CPU or custom metric) REST service for supporting non-RPC connector plugins.

But in the default replicas.yaml properties this service doesn't have autoscaling settings.
Plus, if manually scale this StatefulSet and check get top pod metrics you can see that always work only one Pod and the system doesn't does not distribute loads between few pods, so I have to give this Service a lot of memory and CPU resources.

Could someone describe me why it happens and where I can be wrong?
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant