Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

For Synchronous API requests, Adeptia Connect first checks if the runtime pod has enough cpu and memory available to be considered ready to accept any more request. The application performs this check by using the following two threshold properties for runtime.

  • readiness.probe.cpu.threshold
  • readiness.probe.memory.threshold
PropertyDescription
readiness.probe.cpu.threshold

Threshold value (in percentage of the allocated CPU request) for CPU utilization. If the pod CPU utilization goes beyond this value, the pod will not accept any more requests to process.  Ensure that this threshold value is always greater than the HPA target CPU utilization percentage value that has been set through the environment variable RUNTIME_AUTOSCALING_TARGETCPUUTILIZATIONPERCENTAGE in the global values.yaml file. You can keep the property value blank to skip this threshold check.

readiness.probe.memory.thresholdThreshold value (in percentage of the minimum JVM memory XMS) for application memory utilization. If the application memory utilization goes beyond this value, the pod will not accept any more requests to process.  Ensure that this threshold value is always greater than the HPA target memory utilization percentage value that has been set through the environment variable RUNTIME_AUTOSCALING_TARGETMEMORYUTILIZATIONPERCENTAGE in the global values.yaml file. You can keep the property value blank to skip this threshold check.

You can find these properties at Account >Settings >Microservice Settings >Runtime >Readiness Probe ConfigurationTo know how to configure these properties, refer to the page Configuring the application properties.


Related Topics

Microservice Settings - Runtime

  • No labels