ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

"AXA Transformer" at 400% cpu and App sessions appears but after several hours


Article ID: 238179


Updated On:


CA App Experience Analytics



- Data from applications is visible in AXA but appears after several hours

- "Cluster management" reports "AXA Transformer" CPU at 400% 

How can we solve the issue?


Not enough capacity to process all incoming AXA data


How to verify this condition?

1) connect to a kafka pod:

 kubectl exec -ti <jarvis-kafka-pod> sh -n<namepsace>

2) Check if there is a LAG processing the AXA data

 /opt/ca/kafka/bin/ --bootstrap-server jarvis-kafka:9092,jarvis-kafka-2:9092,jarvis-kafka-3:9092 --describe --group axa.transformer


DX AXA 20.x, 21.x


1) Increase the # of replicas for axa services as below:

kubectl scale --replicas=4 deployment axaservices-transformer -n<namespace>
kubectl scale --replicas=4 deployment axaservices-indexer -n<namespace>
kubectl scale --replicas=4 deployment axaservices-kibana-indexer -n<namespace>
kubectl scale --replicas=4 deployment axaservices-axa-user-processor -n<namespace>
kubectl scale --replicas=2 deployment axaservices-axa-ng-aggregator -n<namespace>

2) Connect to a kafka pod and verify if the LAG issue is resolved


NOTE: You can increase the # of replicas of the above deployments to a maximum of 5, if the problem persist after this, contact Broadcom Support

Additional Information