Timeline for Amazon Web Service (AWS): Spot request active followed by cancelled terminating
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 3, 2018 at 9:13 | vote | accept | Senju | ||
| Jun 1, 2018 at 13:00 | comment | added | Michael - sqlbot | One problem is that spot fulfillment is asynchronous. If you requested on-demand instances that exceeded your allowed capacity, the error would be immediate and explain the problem, and not deferred like you see here. Spot has services talking to services on your behalf; in some cases would a limit exceeded make the spot request impossible to fulfill, in others it wouldn't. | |
| Jun 1, 2018 at 6:06 | answer | added | Senju | timeline score: 0 | |
| Jun 1, 2018 at 6:03 | comment | added | Senju | Running On-Demand EC2 instances: 1 Well.. the error message could be more precise then. Just cancelling the service without notice why isn't the best solution I guess... | |
| May 31, 2018 at 12:06 | comment | added | Michael - sqlbot |
Verify that the instance would not cause you to exceed your limit for that instance type in the region. Find the Limits link in the console.
|
|
| May 31, 2018 at 8:25 | review | First posts | |||
| May 31, 2018 at 14:44 | |||||
| May 31, 2018 at 8:23 | history | asked | Senju | CC BY-SA 4.0 |