mammoth-camera-9096205/12/2023, 4:11 AM
(taking up to hours longer than I would expect). I'll see a number (say 20, but I haven't counted the exact number) resources being provisioned at once, 19 of which are quick to provision (e.g. s3 bucket) and one of which takes a long time (e.g. RDS instance). There are many other resources in the stack that need to be provisioned, which don't depend on the RDS instance in any way, and may or may not depend on the 19 s3 buckets. I would expect that at any given time I would have 20 provisioning operations running at once (as the dependency graph allows), and as the s3 buckets provision that the provisioning operation of another resource would take it's place. However what seems to happen is that the engine waits for all 20 resources in this batch to finish provisioning before starting a new batch of 20, regardless of what the dependency graph would allow. Is this expected? Is it due to how the engine runs and waits on resource creation?
worried-rain-7442005/12/2023, 7:02 PM
mammoth-camera-9096205/18/2023, 2:14 AM
worried-rain-7442005/18/2023, 11:28 AM
mammoth-camera-9096205/19/2023, 7:15 AM
worried-rain-7442005/19/2023, 12:07 PM
what could possibly cause some resources to be blocking futures and not others?Programmer error on the Pulumi-side of things! Sorry if that was unclear. I'm saying it's possible it's a bug.