Load Scheduling based on Java garbage collection times

The following PromQL query (with appropriate filters) is used as SIGNAL for the load scheduler:

avg(java_lang_G1_Young_Generation_LastGcInfo_duration)

Configuration

Blueprint name: load-scheduling/java-gc-generic

Parameters

policy

Parameter	policy.components
Description	List of additional circuit components.
Type	Array of Object (aperture.spec.v1.Component)
Default Value	Expand []

Parameter	policy.policy_name
Description	Name of the policy.
Type	string
Default Value	__REQUIRED_FIELD__

Parameter	policy.resources
Description	Additional resources.
Type	Object (aperture.spec.v1.Resources)
Default Value	Expand flow_control: classifiers: []

policy.load_scheduling_core

Parameter	policy.load_scheduling_core.dry_run
Description	Default configuration for setting dry run mode on Load Scheduler. In dry run mode, the Load Scheduler acts as a passthrough and does not throttle flows. This config can be updated at runtime without restarting the policy.
Type	Boolean
Default Value	false

Parameter	policy.load_scheduling_core.kubelet_overload_confirmations
Description	Overload confirmation signals from kubelet.
Type	Object (kubelet_overload_confirmations)
Default Value	Expand {}

Parameter	policy.load_scheduling_core.overload_confirmations
Description	List of overload confirmation criteria. Load scheduler can throttle flows when all of the specified overload confirmation criteria are met.
Type	Array of Object (overload_confirmation)
Default Value	Expand []

Parameter	policy.load_scheduling_core.aiad_load_scheduler
Description	Parameters for AIMD throttling strategy.
Type	Object (aperture.spec.v1.AIADLoadSchedulerParameters)
Default Value	Expand alerter: alert_name: AIAD Load Throttling Event load_multiplier_linear_decrement: 0.05 load_multiplier_linear_increment: 0.025 load_scheduler: selectors: - control_point: __REQUIRED_FIELD__ max_load_multiplier: 2 min_load_multiplier: 0

Parameter	policy.load_scheduling_core.setpoint
Description	Setpoint.
Type	Number (double)
Default Value	__REQUIRED_FIELD__

policy.jmx

Parameter	policy.jmx.jmx_host
Description	Hostname for scraping metrics provided by JMX Prometheus Java Agent.
Type	string
Default Value	__REQUIRED_FIELD__

Parameter	policy.jmx.jmx_prometheus_port
Description	Port number for scraping metrics provided by JMX Prometheus Java Agent.
Type	Integer (int32)
Default Value	__REQUIRED_FIELD__

---

Schemas

driver_criteria

Parameter	enabled
Description	Enables the driver.
Type	Boolean
Default Value	__REQUIRED_FIELD__

Parameter	threshold
Description	Threshold for the driver.
Type	Number (double)
Default Value	__REQUIRED_FIELD__

---

overload_confirmation_driver

Parameter	pod_cpu
Description	The driver for using CPU usage as overload confirmation.
Type	Object (driver_criteria)
Default Value	Expand {}

Parameter	pod_memory
Description	The driver for using memory usage as overload confirmation.
Type	Object (driver_criteria)
Default Value	Expand {}

---

kubelet_overload_confirmations

Parameter	criteria
Description	Criteria for overload confirmation.
Type	Object (overload_confirmation_driver)
Default Value	__REQUIRED_FIELD__

Parameter	infra_context
Description	Kubernetes selector for scraping metrics.
Type	Object (aperture.spec.v1.KubernetesObjectSelector)
Default Value	__REQUIRED_FIELD__

---

overload_confirmation

Parameter	operator
Description	The operator for the overload confirmation criteria. oneof: `gt | lt | gte | lte | eq | neq`
Type	string
Default Value

Parameter	query_string
Description	The Prometheus query to be run. Must return a scalar or a vector with a single element.
Type	string
Default Value

Parameter	threshold
Description	The threshold for the overload confirmation criteria.
Type	Number (double)
Default Value

---

Dynamic Configuration

note

The following configuration parameters can be dynamically configured at runtime, without reloading the policy.

Parameters

Parameter	dry_run
Description	Dynamic configuration for setting dry run mode at runtime without restarting this policy. In dry run mode the scheduler acts as pass through to all flow and does not queue flows. It is useful for observing the behavior of load scheduler without disrupting any real traffic.
Type	Boolean
Default Value	__REQUIRED_FIELD__

---