You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently found that the minion-manager was not switching from on-demand to spot-instances because it saw that the spot-instance price was > than the on-demand price. The on-demand instance price was seen to be 0.000 :-).
Turns out that this was happening because the AWS on-demand pricing endpoint was returning multiple values for that instance-type for the same region. The current mechanism for gathering the ondemand instance price will simply take the price of the last entry for that instance type. But it seems that that price could be 0.00.
This is what we got in one case:
{'SKU': '2N2QH6UEJZ5GUPT8'
'OfferingClass': ''
'Group': ''
'Instance Capacity - xlarge': ''
'Instance Capacity - 16xlarge': ''
'PricePerUnit': '0.0464000000'
'PriceDescription': '$0.0464 per On Demand Linux t2.medium Instance Hour'
The difference in the three prices is the price description.
'PriceDescription': '$0.0464 per On Demand Linux t2.medium Instance Hour'
'PriceDescription': '$0.0464 per Unused Reservation Linux t2.medium Instance Hour'
'PriceDescription': '$0.00 per Reservation Linux t2.medium Instance Hour'
Basically, minion-manager currently only support on-demand instances (does not support Reserved instances). Therefore, only the "On Demand" price description from the above is relevant. But current implementation of the price querying API does not factor this in.
To start with:
it'll be good to specifically look for "On Demand " in the price description and only consider that price.
Add warnings if there are duplicates and if some price is being overwritten
Ensure that the price is not set to 0. If so... log LOUDLY!!
The text was updated successfully, but these errors were encountered:
We recently found that the minion-manager was not switching from on-demand to spot-instances because it saw that the spot-instance price was > than the on-demand price. The on-demand instance price was seen to be 0.000 :-).
Turns out that this was happening because the AWS on-demand pricing endpoint was returning multiple values for that instance-type for the same region. The current mechanism for gathering the ondemand instance price will simply take the price of the last entry for that instance type. But it seems that that price could be 0.00.
This is what we got in one case:
The difference in the three prices is the price description.
Basically, minion-manager currently only support on-demand instances (does not support Reserved instances). Therefore, only the "On Demand" price description from the above is relevant. But current implementation of the price querying API does not factor this in.
To start with:
The text was updated successfully, but these errors were encountered: