You may notice On-Demand (OD) instances launching even when the Spot instance allocation is configured at 100% in Elastigroup. This behavior is intentional and occurs under certain conditions related to cost optimization and workload stability.
Setting Spot allocation to 100% instructs Elastigroup to prefer Spot instances; however, the algorithm evaluates multiple factors before finalizing instance launches. Spot instances may not always be selected in the following scenarios:
Savings threshold not met
-
Elastigroup requires a minimum Spot savings compared to On-Demand price before opting for Spot.
-
By default, this threshold is 20%. If the available Spot markets offer less than 20% savings, Elastigroup launches OD instances.
-
Example: If Spot prices fluctuate closer to OD cost, stability is prioritized and OD is used.
-
Market availability and interruption risk
-
If Spot markets indicate higher risk of interruption (or insufficient stability), Elastigroup prioritizes availability by launching OD instances.
-
Applies heavily when using Availability-oriented cluster orientation, where continuity is a priority.
Restricted instance type options
-
Configuring a small or narrow whitelist of Spot instance types can reduce viable Spot markets.
-
When not enough suitable Spot markets exist, the algorithm defaults to OD to maintain required capacity.
Risk and cost optimization filters
-
Elastigroup dynamically applies complex filters to ensure capacity, cost optimization, and system safety.
-
This means OD launch is a proactive fallback under certain pricing or operational risk conditions.
Key points to remember
-
Setting Spot to 100% represents preference, not an absolute rule.
-
Cost savings (default 20%) and stability thresholds influence the final decision.
-
OD is utilized as a fallback mechanism to ensure workload continuity and scalability.
If needed, admins can request updating the savings percentage threshold in internal configurations to alter fallback behavior.
Related Articles
Prevent on‑demand instances from reverting to Spot outside configured hours 4Number of Views Reasons on‑demand nodes can run in Ocean AKS virtual node groups 5Number of Views Why an on-demand instance launches while Spot capacity exists in other markets 8Number of Views How On-Demand instance types are selected in Elastigroup? 10Number of Views Fix the “Cannot set both ‘ondemand’ and ‘onDemandTypes’ parameters” message 4Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago