High Response time on /signin/token API
book
Article ID: 271997
calendar_today
Updated On:
Feedback
Subscribe
Products
Symantec Identity Security Platform - IDSP (formerly VIP Authentication Hub)
Show More
Show Less
Issue/Introduction
High response time is observed on /signin/token API, although all other API were responding quickly. How we can I can increase/scale up the signin pod to remedy this situation?
Environment
Release : AuthHub 2022.Oct.06, 2.1.x
Resolution
Run the following command and find the signin pod's Horizontal Pod Autoscaler (hpa) object
kubectl get hpa -n ssp
$ k get hpa -n ssp NAME REFERENCE TARGETS MINPODS MAXPODS REPLICAS AGE ssp-ssp-admin-hpa Deployment/ssp-ssp-admin 2%/80% 1 1 1 377d ssp-ssp-adminconsole-hpa Deployment/ssp-ssp-adminconsole 0%/80% 1 1 1 377d ssp-ssp-auth-mgr-hpa Deployment/ssp-ssp-auth-mgr 2%/80% 1 1 1 377d ssp-ssp-azserver-hpa Deployment/ssp-ssp-azserver 1%/80% 1 1 1 377d ssp-ssp-factor-hpa Deployment/ssp-ssp-factor 1%/80% 1 1 1 377d ssp-ssp-iarisk-hpa Deployment/ssp-ssp-iarisk 1%/80% 1 1 1 377d ssp-ssp-opa-hpa Deployment/ssp-ssp-opa 0%/80% 1 1 1 377dssp-ssp-signin-hpa Deployment/ssp-ssp-signin 0%/80% 1 1 1 377d
and then run
kubectl edit hpa ssp-ssp-signin-hpa -n ssp
and increase maxReplicas and minReplicas values accordingly.
Feedback
thumb_up
Yes
thumb_down
No