The changed Instance Type will not be reflected on the Hardware page for the Data Hub but rather show the original setting.
Reconfiguration of the DataHub can be done in place for existing DataHubs. For new DataHubs, we recommend that you use the instance type selector from the Advanced menu to pick the desired instance type.
The DataHub will be stopped during the reconfiguration. Expect an outage that lasts for about 4 hours.
Stop the DataHub cluster
Change Data Hub instance type
Change the Data Hub root volume size (optional)
Start the DataHub
Validate the DataHub
Stop the DataHub Cluster
Locate the DataHub on the Management Console.
Invoke the Stop DataHub action.
Change Instance Type
Note. Ensure that you choose an instance type that has been tested by Cloudera. For a list of appropriate instance types please consult
(Data Hub - AWS Instances list)
You change the instance type for the Master Node for the Data Hub.
Using the Management Console for the Data Hub, select the Hardware tab and locate the instance ID for the master node.
Using AWS Console→EC2→Instance, locate the instance that matches the instance ID for the master node.
Select the Instance. Select Actions→Instance settings→Change instance type.
Choose an instance type supported by Cloudera. This example doubles the instance size from m5.2xlarge to m5.4xlarge, or m5.8xlarge depending on your needs, please use the same instance, family, during the procedure.
Click Apply. Check that the instance type has been changed to your desired choice.
Change the Size of the Root Volume (optional)
The root volume size may be too small for production usage. You can resize it using the following procedure.
Using the AWS Console, go to the instance ID you want to change. Make sure you're selecting the instance for the Master node.
Click on the Storage tab. Click on the root volume (usually the first volume attached to the VM).
Select Action→Modify Volume to open the Modify Volume dialog.
In the Modify Volume dialog box, select a new size for the root volume. Click the Modify button.
Verify that the volume has been resized by clicking on the reload button at the top of the page.
Start DataHub Cluster
Use the Management Console to start the DataHub cluster
Validate the DataHub
The simplest way to validate the changes is sshing into the VM(s) what you have changed and inspect the desired memory, CPU, and disk space with the appropriate Linux commands: