Closed asias closed 1 week ago
@asias for the meantime, can you use without capacity reservation? (btw. do you hit issues with AWS capacity in this test?)
@asias for the meantime, can you use without capacity reservation? (btw. do you hit issues with AWS capacity in this test?)
I disabled it as soon as I found it is the culprit. No I did not hit capacity issue so far, which I assume you meant could not allocate instances in the middle of the test.
@asias for the meantime, can you use without capacity reservation? (btw. do you hit issues with AWS capacity in this test?)
I disabled it as soon as I found it is the culprit. No I did not hit capacity issue so far, which I assume you meant could not allocate instances in the middle of the test.
this feature helps making sure you get all the allocation need upfront in the beginning of the test, and no surprises during the test itself.
it also have the ability to fallback to next AZ, if there no capacity in the select AZ
it mostly for general stability of jobs we are running regularly, for your case it's probably not really needed.
With the following yam config, sct fails to run
n_db_nodes: '2 2' nemesis_add_node_cnt: 3 use_capacity_reservation: true