guineveresaenger
commented
1 month ago Hi @anitalySuper, thank you for reporting this bug. We're sorry that this happened.
I'm unfortunately unable to reproduce this behavior exactly; our test account is not of a high enough tier to allow for multi-cluster warehouses.
I did do the following:
Run pulumi up with the following YAML file:
`name: snowflake-673
runtime: yaml
description: A minimal Pulumi YAML program
config: {'pulumi:tags': {value: {'pulumi:template': yaml}}}
resources:
kafka-warehouse--warehouse--object:
type: snowflake:Warehouse
properties:
autoResume: true
autoSuspend: 60
name: KAFKA_WAREHOUSE
resourceMonitor: null
warehouseSize: XSMALL
enableQueryAcceleration: false
options:
version: 0.55.0Relevant section of stack file:
"inputs": {
"__defaults": [
"comment",
"maxConcurrencyLevel",
"queryAccelerationMaxScaleFactor",
"statementQueuedTimeoutInSeconds",
"statementTimeoutInSeconds",
"warehouseType"
],
"autoResume": true,
"autoSuspend": 60,
"comment": "",
"enableQueryAcceleration": false,
"maxConcurrencyLevel": 8,
"name": "KAFKA_WAREHOUSE",
"queryAccelerationMaxScaleFactor": 8,
"statementQueuedTimeoutInSeconds": 0,
"statementTimeoutInSeconds": 172800,
"warehouseSize": "XSMALL",
"warehouseType": "STANDARD"Update the version field to 0.56.0 and explicitly set `maxConcurrencyLevel:
name: snowflake-673
runtime: yaml
description: A minimal Pulumi YAML program
resources:
kafka-warehouse--warehouse--object:
type: snowflake:Warehouse
properties:
autoResume: true
autoSuspend: 60
name: KAFKA_WAREHOUSE
resourceMonitor: null
warehouseSize: XSMALL
maxConcurrencyLevel: 8
enableQueryAcceleration: false # I cannot set this to true due to now having an Enterprise subscription
options:
version: 0.56.0The upgrade succeds for me. Relevant stack.json output:
"parameters": [
{
"maxConcurrencyLevels": [
{
"default": "8",
"description": "Maximum number of SQL statements a warehouse cluster can execute concurrently before queuing them. Small SQL statements count as a fraction of 1.",
"key": "MAX_CONCURRENCY_LEVEL",
"level": "WAREHOUSE",
"value": "8"
}
],
"statementQueuedTimeoutInSeconds": [
{
"default": "0",
"description": "Timeout in seconds for queued statements: statements will automatically be canceled if they are queued on a warehouse for longer than this amount of time; disabled if set to zero.",
"key": "STATEMENT_QUEUED_TIMEOUT_IN_SECONDS",
"level": "WAREHOUSE",
"value": "0"
}
],
"statementTimeoutInSeconds": [
{
"default": "172800",
"description": "Timeout in seconds for statements: statements are automatically canceled if they run for longer; if set to zero, max value (604800) is enforced.",
"key": "STATEMENT_TIMEOUT_IN_SECONDS",
"level": "",
"value": "172800"
}
]
}
],
"queryAccelerationMaxScaleFactor": 8,My best guess is that there's something about the additional parameters that you're setting for your multi-cluster warehouses are not playing well together.
One thing you could try is set `"enableQueryAcceleration": "true", or try tweaking some of the other affected defaults changes.
Please let us know how it goes!
anitalySuper
VenelinMartinov
Describe what happened
Updated to pulumi-snowflake v.0.56.0. Per the migration guide, I added in the value of 8 for maxConcurrencyLevel for every warehouse (this was previously not directly set in Pulumi as each warehouse would take on the default value of 8). Note, I was just specifying the default value and did not change the value.
When running
pulumi up, I get a series of errors:And
Sample program
This is the corresponding yaml:
Below is the corresponding state after running
pulumi up:Log output
No response
Affected Resource(s)
Warehouses
Output of
pulumi aboutAdditional context
No response
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).