You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
In the Survival Guide I see this information for "classic-rest-service":
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
The text was updated successfully, but these errors were encountered: