Need help?

Our experts have had an average response time of 12.14 minutes in September 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

Unable to Perform Elastic Resize for Amazon Redshift Cluster

by | Aug 8, 2021

Unable to Perform Elastic Resize for Amazon Redshift Cluster? We can help you.

Recently, one of our customers tried to perform an elastic resize via AWS CloudFormation for his Amazon Redshift cluster.

However, it performed a classic resize instead.

Here, at Bobcares, we assist our customers with several AWS queries as part of our AWS Support Services.

Today, let us see what leads to this and how we can troubleshoot it.


Unable to Perform Elastic Resize for Amazon Redshift Cluster

If we resize the cluster using the Amazon Redshift console, it does not register in the AWS CloudFormation template.

Instead, if we use the AWS CloudFormation template we can ensure that the numberofNodes parameter updates.

Otherwise, Amazon Redshift might perform a classic resize, despite meeting the resize requirements.

This behavior is a result when there are no changes to the node count since its last resize.

Generally, a classic resize by Amazon Redshift happen if we don’t meet any of these requirements:

  • Only the numberofNodes parameter modifies.
  • For dc2.large or ds2.xlarge node types, we can only double the node count or decrease the node count by half of the original cluster.
  • Similarly, for dc2.8xlarge or ds2.8xlarge node types, we can resize up to two times the original node count, or resize down to half of the original node count.
  • The number of nodes cannot exceed the number of slices.


How to Troubleshoot?

To confirm the actual number of nodes in the cluster, we can check the Amazon Redshift console.

Then we can verify if it matches the numberofNodes parameter in the AWS CloudFormation template.

To retrieve information from AWS CloudTrail and to determine root cause analysis, we can use the DescribeClusters API.

We look at the elasticResizeNumberOfNodeOptions parameter to verify whether the Amazon Redshift cluster is eligible for an elastic resize.

Suppose, the parameter does not list an option to update node count.

This confirms that the cluster slices fail to meet the elastic resize requirements.

[Stuck with the Elastic Resize? We’d be happy to help you out]



In short, we saw how our Support Techs troubleshoot the Elastic Resize issue with the Amazon Redshift Cluster.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.