Set --create_and_boot_post_delay to 2 seconds by default. #2910
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![copybara-service[bot]](https://avatars.githubusercontent.com/in/44061?s=60&v=4){kind=small}
EC2 seems to have a race condition when adding VMs to a clustered placement group. If you call `aws ec2 run-instances` in parallel adding multiple VMs to a clustered placement group, it incorrectly claims: ``` The perfkit-db9d2a668-731b3c6e8f4b Placement Group has already been used in another Availability Zone. Specify the correct Availability Zone and try again. ``` Sleep two seconds to boot this. If you want to measure how fast a cloud can boot many VMs without this sleep, use the large_scale_boot benchmark, which does not use clustered placement groups and uses a single run_instances command on AWS. If you would like to repro the race condition run: ``` ./pkb.py --benchmarks=cluster_boot --cloud=AWS --num_vms=20 --create_and_boot_post_task_delay=0 ``` PiperOrigin-RevId: 372371889
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Set --create_and_boot_post_delay to 2 seconds by default.
EC2 seems to have a race condition when adding VMs to a clustered placement group.
If you call
aws ec2 run-instancesin parallel adding multiple VMs to a clustered placement group, it incorrectly claims:Sleep two seconds to boot this.
If you want to measure how fast a cloud can boot many VMs without this sleep, use the large_scale_boot benchmark, which does not use clustered placement groups and uses a single run_instances command on AWS.
If you would like to repro the race condition run: