Redshift wlm queue rules update#

Though, it doesn't say that the default queue can't have any User or Query groups. If it manages the memory on its own, the performance of your cluster would be unpredictable.īut yeah, I agree that the Redshift documentation lacks clarity on this. Redshift doesn't have any configuration of how you'd like the 13% memory to be allocated to these queries. What if 100 concurrent queries came from UG5. You might counter-argue that Redshift can use the remaining 13% memory. Which queue does it get routed to? A default queue helps in such a case. Now, a User from another User group, say UG5, queries Redshift. Let's say you have four queues, each of which has a different User group, say, UG1, UG2, UG3 and UG4. one which doesn't have any User or Query groups) as the last one. However, it is easy to guess why Redshift requires a default queue (i.e. Previously, I had four queues, each with an assigned user group I am not sure about this statement of yours:

Redshift wlm queue rules update#

I didn't see an update on their official blog, I don't see this mentioned in the docs, or the doc updates (, ) This is blocking me from making other desired changes to the existing queues. Now, I have no problem creating this new queue, but I would really like to see an explicit explanation of what it does/what its affects are before I do it. It didn't add up to 100%, and supposedly the rest was dynamically managed by redshift. My main question is where is this need for a new 'non-user' queue explained? This is definitely a change because previously, I had four queues, each with an assigned user group, and their collective memory allocation was 87%. That's annoying because adding a new queue requires cluster reboot, but that's not the reason I'm asking this question. Now, the obvious solution is to just create a new queue with no user group specified and give it the remaining amount of memory so that it all adds up to 100%. The final queue may not contain User Groups or Query Groups. The following problems must be corrected before you can save this workload configuration: I want to update the WLM configuration for my Redshift cluster, but I am unable to make changes and save them due to the following message displayed: