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
I felt ambitious today and tried to list 17 accounts in 17 regions.
awsls failed before listing anything.
$ awsls cloudtrail --regions "${regions}" --profiles "${profiles}"
Error: failed to launch provider (/home/isme/.awsls/terraform-provider-aws_v3.31.0_x5): pipe2: too many open files
I'm not really sure what limit I'm hitting here, whether it's imposed by awsls itself or by my operating system.
When I halved the number of regions to 8, the behavior was unpredictable and unstable.
Hi @iainelder, I started working on the first issues that you are describing. All provider plugins (17x17=289) are launched in the beginning and lead to too many open files. I'll try to launch/close the provider each time when needed (this is also what Terraform does and the overhead of launch/close is very small): #39
I felt ambitious today and tried to list 17 accounts in 17 regions.
awsls failed before listing anything.
I'm not really sure what limit I'm hitting here, whether it's imposed by awsls itself or by my operating system.
When I halved the number of regions to 8, the behavior was unpredictable and unstable.
Once it froze for a while before printing:
Another time it printed something more esoteric:
I suppose there is a certain stable limit for the number of accounts and regions I can query.
Is there some way to control the concurrency of awsls without splitting the calls into batches?
The text was updated successfully, but these errors were encountered: