I repeated the 1000 instances test with t2.nano instances. AWS provider spun up around 5000 instances, mainly because the registering takes longer time than the provisioning loop. I am suspending further testing to eliminate the bugs found. I'll link the tickets to this one.
Bug 1577837 Comment 9 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I repeated the 1000 instances test with t2.nano instances. AWS provider spun up around 5000 instances, mainly because the registering takes longer time than the provisioning loop. Another error encountered was `InsufficientFreeAddressesInSubnet: insufficient free addresses to allocate 1000 addresses in subnet`. We need to make sure the load is being spread over subnets/regions. Along with this, we need to make sure the requests are idempotent or something like that. I am suspending further testing to eliminate the bugs found. I'll link the tickets to this one.
I repeated the 1000 instances test with t2.nano instances. AWS provider spun up around 5000 instances, mainly because the registering takes longer time than the provisioning loop. Another error encountered was `InsufficientFreeAddressesInSubnet: insufficient free addresses to allocate 1000 addresses in subnet`. We need to make sure the load is being spread over subnets/regions. Along with this, we need to make sure the requests are idempotent or something like that, otherwise it would be even worse than it is now. I am suspending further testing to eliminate the bugs found. I'll link the tickets to this one.